Python 2.5 environment uses Python 2.7 interpreter

Issue #269 on hold
Torf created an issue

When I use tox to create a Python 2.5 environment it somehow picks up a Python 2.7 interpreter instead. All other Python versions work fine, as does Python 2.5 on its own:

$ cat tox.ini 
envlist = py25,py26,py27,py33,py34
skipsdist = True

commands = python --version

$ tox
py25 installed: wheel==0.24.0
py25 runtests: PYTHONHASHSEED='285314601'
py25 runtests: commands[0] | python --version
Python 2.7.6
py26 installed: argparse==1.3.0,wheel==0.24.0
py26 runtests: PYTHONHASHSEED='285314601'
py26 runtests: commands[0] | python --version
Python 2.6.9
py27 installed: wheel==0.24.0
py27 runtests: PYTHONHASHSEED='285314601'
py27 runtests: commands[0] | python --version
Python 2.7.6
py33 create: /home/torf/tmp/toxtest/.tox/py33
py33 installed: wheel==0.24.0
py33 runtests: PYTHONHASHSEED='285314601'
py33 runtests: commands[0] | python --version
Python 3.3.6
py34 create: /home/torf/tmp/toxtest/.tox/py34
py34 installed: wheel==0.24.0
py34 runtests: PYTHONHASHSEED='285314601'
py34 runtests: commands[0] | python --version
Python 3.4.0
______________ summary ______________
  py25: commands succeeded
  py26: commands succeeded
  py27: commands succeeded
  py33: commands succeeded
  py34: commands succeeded
  congratulations :)

$ python2.5 --version
Python 2.5.6

$ .tox/py25/bin/python --version
Python 2.7.6

$ tox --version
2.1.1 imported from /usr/local/lib/python2.7/dist-packages/tox/__init__.pyc

This is on Ubuntu 14.04.

Comments (5)

  1. Torf reporter

    With the help of @The-Compiler on IRC I noticed that .tox/py25/.tox-config1 contains a link to /usr/lib/python which is indeed 2.7.6 and not 2.5. Not sure what that means, but maybe it helps...

    @The-Compiler also suggested to add the following to my tox.ini:


    That results in

    $ tox
    py25 recreate: /home/torf/tmp/toxtest/.tox/py25
    ERROR: UnsupportedInterpreter: python2.5 is not supported anymore, sorry

    At that point I realized that tox hasn't supported Python 2.5 since version 1.17.0 (I'm running 2.1.1).

    Nevertheless I wonder why I didn't get that error message in the first place, i.e. why tox picked a wrong Python version.

  2. Holger Krekel repo owner

    not sure either why tox didn't report an error but indeed python2.5 is not supported so i don't like to investigate, sorry.

  3. Torf reporter

    @hpk42: That's fine with me. As I've written above I only noticed halfway through this problem that 2.5 isn't supported anymore.

  4. Log in to comment