I've just verified that what changed was a change in behavior from pylint from 1.5.4 to 1.5.5 (which was uploaded 2016-03-21) https://pypi.python.org/pypi/pylint .
this is the crux of using tox.
Its obnoxious when some upload somewhere on the internet starts breaking your c-i.
The thing we could do is set the version of pylint that is installed explicitly.
That can be done with something like:
=== modified file 'tox.ini'
--- tox.ini 2016-03-18 14:05:02 +0000
+++ tox.ini 2016-03-30 23:43:34 +0000
@@ -38,7 +38,7 @@
# set basepython because tox 1.6 (trusty) does not support generated environments
basepython = python3
deps = {[testenv]deps}
- pylint
+ pylint==1.5.4
bzr+lp:simplestreams
commands = {envpython} -m pylint --errors-only {posargs:curtin tests/vmtests}
I've just verified that what changed was a change in behavior from pylint from 1.5.4 to 1.5.5 (which was uploaded 2016-03-21) https:/ /pypi.python. org/pypi/ pylint .
this is the crux of using tox.
Its obnoxious when some upload somewhere on the internet starts breaking your c-i.
The thing we could do is set the version of pylint that is installed explicitly.
That can be done with something like:
=== modified file 'tox.ini'
--- tox.ini 2016-03-18 14:05:02 +0000
+++ tox.ini 2016-03-30 23:43:34 +0000
@@ -38,7 +38,7 @@
# set basepython because tox 1.6 (trusty) does not support generated environments
basepython = python3
deps = {[testenv]deps}
- pylint
+ pylint==1.5.4
bzr+lp:simplestreams
commands = {envpython} -m pylint --errors-only {posargs:curtin tests/vmtests}