302ba18d81
The check_constraints utility wraps a new check_exists cmd.
This command looks at a project's requirements and checks:
- That the requirement name alone exists in both g-r and u-c
- If it exists in both, then check that the version in u-c
is covered.
- Added an extra g-r check as a flag, but not quite happy with it.
It needs more work.. but would be a _little_ more correct
if/when g-r stops defining the minimum.
This patch is currently WIP as tests are still required. But is
the starting point for the fuzzy checking for projects managing
their own lower-constraints.
Change-Id: I36690fddcfc24d49aab0d28d7d46dcd8d9128b2a
20 lines
332 B
Plaintext
20 lines
332 B
Plaintext
hacking>=0.5.6,<0.7
|
|
coverage>=3.6
|
|
discover
|
|
feedparser
|
|
fixtures>=0.3.12
|
|
mox==0.5.3
|
|
mox3==0.21.0
|
|
MySQL-python
|
|
psycopg2
|
|
pylint==0.25.2
|
|
# Imported by ldapdns so required to generate
|
|
# the sample configuration file
|
|
python-ldap==2.3.13
|
|
python-subunit
|
|
setuptools_git>=0.4
|
|
sphinx>=1.1.2
|
|
oslo.sphinx
|
|
testrepository>=0.0.13
|
|
testtools>=0.9.27
|