uncap SQLA in requirements.txt

migrate can't just take a global requirements sync because it
needs to be tested against multiple versions of SQLA to assure
compatibility. A recent change had the effect of only testing
migrate against SQLA 0.7, which is definitely *not* what we
want to be doing.

this reverts that change, and leaves very specific comments to
hopefully prevent this from happening in the future.

Change-Id: Icb4e136f0de6caa224019bb955341c4b67c5e1a1
This commit is contained in:
Sean Dague 2014-02-23 11:08:25 -05:00
parent d58e47f85c
commit fe148d87b4
2 changed files with 12 additions and 1 deletions

View File

@ -1,5 +1,8 @@
pbr>=0.5.21,<1.0
SQLAlchemy>=0.7.8,<=0.7.99
# never put a cap on this, *ever*, sqla versions are handled via
# tox, and if SQLA is capped it will only make it so we aren't testing
# against all the versions we are compatible with.
SQLAlchemy>=0.7.8
decorator
Tempita >= 0.4

View File

@ -12,6 +12,14 @@ deps = -r{toxinidir}/requirements.txt
commands =
python setup.py testr --slowest --testr-args='{posargs} --concurrency=1'
[testenv:py26]
deps = sqlalchemy>=0.8,<=0.8.99
-r{toxinidir}/test-requirements.txt
[testenv:py27]
deps = sqlalchemy>=0.8,<=0.8.99
-r{toxinidir}/test-requirements.txt
[testenv:py26sa07]
basepython = python2.6
deps = sqlalchemy>=0.7,<=0.7.99