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
..
cmds	Add the concept of a version map for constraints generation	2016-10-06 16:22:18 +11:00
tests	Add the concept of a version map for constraints generation	2016-10-06 16:22:18 +11:00
__init__.py	Move tests into openstack_requirements.	2015-06-08 22:07:01 +12:00
constraints.py	Add wheel to UNCONSTRAINABLE	2016-04-05 06:39:29 -04:00
project_config.py	add a validation command to ensure projects use check-requirements	2016-05-12 16:15:46 -04:00
project.py	Use ConfigParser instead of SafeConfigParser	2016-09-29 08:57:54 +00:00
requirement.py	Integrate normalize as part of the requirements tools	2016-06-23 10:16:23 +02:00