--- you can reply above this line --- New issue 87: Tox obeys the VIRTUALENV_PYTHON environment variable if set https://bitbucket.org/hpk42/tox/issue/87/tox-obeys-the-virtualenv_python
Mathieu Agopian: This means that if somebody is settings this variable in his .bashrc file for example, in order to have his own manually created virtualenvs use a specific version of python by default (say python2.7), tox will create all venvs with the same python interpreter, whatever the envlist. I can see three solutions to this: * don't do anything: maybe add a FAQ entry or note somewhere in the doc or in a troubleshooting session explaining this behaviour * unset the environment variable before creating the virtualenvs * create virtualenvs using the --python option and pass it the env (this way the VIRTUALENV_PYTHON isn't used) I'd go for the third option, thoughts? -- This is an issue notification from bitbucket.org. You are receiving this either because you are the owner of the issue, or you are following the issue. _______________________________________________ pytest-commit mailing list pytest-commit@python.org http://mail.python.org/mailman/listinfo/pytest-commit
