|Zuul 27762cda83 Merge "Fixed "pip-install" test"||9 months ago|
|.zuul.d||10 months ago|
|babel-test||3 years ago|
|doc/source||1 year ago|
|openstack_requirements||10 months ago|
|playbooks||10 months ago|
|tools||9 months ago|
|.gitignore||11 months ago|
|.gitreview||6 years ago|
|.stestr.conf||1 year ago|
|MANIFEST.in||5 years ago|
|README.rst||10 months ago|
|bindep.txt||1 year ago|
|blacklist.txt||10 months ago|
|detail.py||1 year ago|
|global-requirements.txt||10 months ago|
|projects.txt||11 months ago|
|requirements.txt||1 year ago|
|setup.cfg||10 months ago|
|setup.py||2 years ago|
|test-requirements.txt||1 year ago|
|tox.ini||10 months ago|
|update.py||3 years ago|
|upper-constraints-xfails.txt||1 year ago|
|upper-constraints.txt||9 months ago|
Refer to the Dependency Management section of the Project Team Guide for information about the history of the project and the files involved.
All the tools require openstack_requirements to be installed (e.g. in a Python virtualenv). They all have help, which is the authoritative documentation.
This will update the requirements in a project from the global requirements file found in
.. Alternatively, pass
--source to use a different global requirements file:
update-requirements --source /opt/stack/requirements /opt/stack/nova
Entries in all requirements files will have their versions updated to match the entries listed in the global requirements. Excess entries will cause errors in hard mode (the default) or be ignored in soft mode.
Compile a constraints file showing the versions resulting from installing all of
generate-constraints -p /usr/bin/python2.7 -p /usr/bin/python3 \ -b blacklist.txt -r global-requirements.txt > new-constraints.txt
Replace all references to a package in a constraints file with a new specification. Used by DevStack to enable git installations of libraries that are normally constrained:
edit-constraints oslo.db "-e file://opt/stack/oslo.db#egg=oslo.db"
Combine multiple lower-constraints.txt files to produce a list of the highest version of each package mentioned in the files. This can be used to produce the "highest minimum" for a global lower constraints list (a.k.a., the "TJ Maxx").
To use the script, run:
$ tox -e venv -- build-lower-constraints input1.txt input2.txt
Where the input files are lower-constraints.txt or requirements.txt files from one or more projects.
If the inputs are requirements files, a lower constraints list for the requirements is produced. If the inputs are lower-constraints.txt, the output includes the highest version of each package referenced in the files.
Run the validation checks from the
requirements-check job locally using the
requirements-check tox environment.
$ tox -e requirements-check -- /path/to/repo/to/test
Look at the Review Guidelines and make sure your change meets them.
All changes to
global-requirements.txt may dramatically alter the contents of
upper-constraints.txt due to adding or removing transitive dependencies. As such you should always generate a diff against the current merged constraints, otherwise your change may fail if it is incompatible with the current tested constraints.
Regenerating involves five steps.
Install the dependencies needed to compile various Python packages:
sudo apt-get install $(bindep -b)
Create a reference file (do this without your patch applied):
generate-constraints -p /usr/bin/python2.7 -p /usr/bin/python3 \ -b blacklist.txt -r global-requirements.txt > baseline
Apply your patch and generate a new reference file:
generate-constraints -p /usr/bin/python2.7 -p /usr/bin/python3 \ -b blacklist.txt -r global-requirements.txt > updated
diff -p baseline updated
upper-constraints.txt. This may require some fiddling.
edit-constraintcan do this for you when the change does not involve multiple lines for one package.