10fb194613
From the ML discussion there was a desire to provide a more detailed version of the requirements that has information such as license, author... This script gathers such information from the pypi json API and writes it to corresponding files that can be used by automated programs that want to determine this information without having to go to pypi themselves. This can be useful for doing requirement license auditing for example. To run: $ python detail.py global-requirements.txt This will gather the information about the requirements from pypi (if possible) and then write a new file located at global-requirements.json with this information. Change-Id: I710feb7038eec0c916593cce0837823e7f4fce15 |
||
|---|---|---|
| tests | ||
| .gitignore | ||
| .gitreview | ||
| .testr.conf | ||
| MANIFEST.in | ||
| README.rst | ||
| detail.py | ||
| dev-requirements.txt | ||
| global-requirements.txt | ||
| projects.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
| update.py | ||
README.rst
Global dependencies for OpenStack Projects
All official OpenStack projects should be added to projects.txt. Once they are added here the gate/check jobs for the projects will use the OpenStack internal pypi mirror to ensure stability. The continuous integration infrastructure will also sync up the requirements across all the official projects and will create reviews in the participating projects for any mis-matches.
This process above will ensure that users of OpenStack will have one single set of python package requirements/ dependencies to install and run the individual OpenStack components.
To use this, run:
python update.py path/to/project
Entries in requirements.txt and test-requirements.txt will have their versions updated to match the entires listed here. Any entries in the target project which do not first exist here will be removed. No entries will be added.