From 7e0f31a5bb82400d6a7e75c5256147e0635f2d93 Mon Sep 17 00:00:00 2001 From: Sean Dague Date: Sat, 28 Sep 2013 07:39:25 -0400 Subject: [PATCH] add an explanation to the sqla requirement people keep trying to "fix" this to a broken statement, and I now realize the reasons for this being added are basically lore lost in the mists of time. So document it. The wrong fix is no longer blocked in our gate because we force install newer pip on our devstack nodes (otherwise lots of other things break). Change-Id: I048e33d101a0c09adabac6d17cbc0ff23fba19e7 --- global-requirements.txt | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/global-requirements.txt b/global-requirements.txt index 11e0ab139a..54a84b3453 100644 --- a/global-requirements.txt +++ b/global-requirements.txt @@ -82,6 +82,11 @@ Routes>=1.12.3 simplejson>=2.0.9 six sockjs-tornado>=1.0.0,<2.0.0 +# The SQLA requirement looks weird, but it's here for a reason. +# The version of pip shipped with distros treats 0.8beta1 (which is +# on pypi) as < 0.8 so the "clear" version of this requirement, is +# actually broken. The fix for this isn't until pip 1.4.1, which is +# way more current than what most distros have. SQLAlchemy>=0.7.8,<=0.7.99 sqlalchemy-migrate>=0.7.2 stevedore>=0.10