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
..
__init__.py	Move commands into cmds subdir.	2015-06-29 15:27:25 +12:00
check_conflicts.py	Fixes for check-uc jenkins job	2016-09-29 20:33:34 +02:00
edit_constraint.py	Add Windows as supported operating system	2016-02-26 14:25:50 +02:00
generate.py	Add the concept of a version map for constraints generation	2016-10-06 16:22:18 +11:00
normalize_requirements.py	Add --save option to normalize-requirements command	2016-06-23 22:27:22 +02:00
update.py	Check that the argument is in fact a directory	2016-05-23 14:09:52 +10:00
validate_projects.py	add a validation command to ensure projects use check-requirements	2016-05-12 16:15:46 -04:00
validate.py	Move data validation out of the unit tests and strengthen	2015-08-03 20:45:37 +00:00