We need to generate constraints for all python versions we use. This is
python 2.7 (trusty and xenial), 3.4 (trusty) and 3.5(xenial). There
isn't a supportable way to install all 3 versions on a single node.
Add a version-map that allows us to clone the output of a freeze between
python versions. This assumes that the python version in question are
compatible during the transition window.
It's possible to run with:
... --version-map 3.4:3.5 --version-map 3.5:3.4 ...
This will mean that we generate constraints consistently between versions
regardless of which version /usr/bin/python3 is.
Change-Id: I55a3597ea2f2bf48e30dc564a4bf4b2ef7f178b3
In change id I60adf0dca4aa32f4ef6bca61250b375c8a3703c6, we added
flake8_docstrings to the black list. However as seen in
I8bfff1b2e65541959e7f2ae0fa6ca6c17889eb54, the generate-constraints
job ends up proposing adding "flake8-docstrings===0.2.1.post1" to
the upper-constraints.txt. This is because of the '-' vs '_'
difference. So just like in Ibaa22657a2cf2c0ad96dbd0b9bc43cdafe6a1d56,
we need to convert the items in black list to the correct safe name
before trying to check if the item is in the black list.
Change-Id: Ieb1cd44e908b80d58a20bf0d0e1e6b10f17ae95e
This script when run creates a constraints file with exact pins for
the transitive dependencies of a requirements file.
Change-Id: I1282f8e4010c0ec46c473495bacddf044d06c0af