Open benjaminp opened 9 years ago
I ran into this problem on a fedora 25 machine with python 2.7.13 and many packages. After a fair bit of experimentation, I managed to boil it down to the following minimal setup that reproduces the same behavior.
cat <<'.'>/tmp/r appdirs==1.4.3 betamax==0.8.0 certifi==2017.4.17 chardet==3.0.3 idna==2.5 packaging==16.8 pika==0.10.0 py==1.4.33 pyparsing==2.2.0 PySocks==1.6.7 pytest==2.9.2 requests==2.16.5 six==1.10.0 urllib3==1.21.1 . virtualenv /tmp/f3 . /tmp/f3/bin/activate pip install -r /tmp/r
** at this point, the virtualenv will produce the problem if pointed at a copy of six that's been built: py.test test_six.py
The virtualenv can then be "fixed" by running one of these 2: pip install -U pytest (pytest 3.1.0 works.)
So I'm not quite sure how I would describe this problem. Bugs arising from complex interaction of non-minimal set of out of date python components?
Originally reported by: jlec (Bitbucket: jlec, GitHub: jlec)