requirements/openstack_requirements/tests
Tony Breeds ffe658de93 Add the concept of a version map for constraints generation
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
2016-10-06 16:22:18 +11:00
..
files Drop hgtools 2016-05-27 09:19:17 +00:00
__init__.py Move tests into openstack_requirements. 2015-06-08 22:07:01 +12:00
common.py Move commands into cmds subdir. 2015-06-29 15:27:25 +12:00
test_constraints.py Move data validation out of the unit tests and strengthen 2015-08-03 20:45:37 +00:00
test_edit_constraint.py Deal with underscores in names in edit-constraints 2015-09-17 10:12:11 +12:00
test_generate.py Add the concept of a version map for constraints generation 2016-10-06 16:22:18 +11:00
test_project.py Add checks for setup.cfg existence in project dictionary 2015-07-15 11:08:48 +03:00
test_requirement.py Revert "Tolerate both new and old setuptools" 2016-03-15 21:05:40 -04:00
test_update_pbr.py Move commands into cmds subdir. 2015-06-29 15:27:25 +12:00
test_update_suffix.py Move commands into cmds subdir. 2015-06-29 15:27:25 +12:00
test_update.py Quick wins for python3 support 2016-09-29 16:48:46 +10:00