Right - all changes to requirements.txt in a project must be already
in global-requirements. So propose it there, get that merged, then
propose into your local project.
-Rob
On 13 July 2015 at 17:08, Qiming Teng wrote:
> Hi,
>
> Tried these in requirements.txt:
>
> Routes!=2.0,!=2.1,>=1.12.3;pyt
Hi,
Tried these in requirements.txt:
Routes!=2.0,!=2.1,>=1.12.3;python_version=='2.7'
Routes!=2.0,>=1.12.3;python_version!='2.7'
The gate still complains:
Requirement set([Requirement(package=u'Routes', location='',
specifiers='!=2.0,!=2.1,>=1.12.3', markers=u"python_version=='2.7'",
comment=''
Yes. Use environment markers to specify<= 2 for portion 2.7 and uncapped
for 3.4.
On 4 Jul 2015 2:19 pm, "Qiming Teng" wrote:
>
> The recent change to global-requirements is excluding both 2.0 and 2.1
> version of Routes. That is forcing us to use Routes 1.13. However,
> Routes 1.13 cannot pass p
The recent change to global-requirements is excluding both 2.0 and 2.1
version of Routes. That is forcing us to use Routes 1.13. However,
Routes 1.13 cannot pass py34 tests due to errors like this:
"/home/jenkins/workspace/gate-senlin-python34/.tox/py34/lib/python3.4/site-packages/routes/route.py
