github.com_fedora-python_to.../tests/fixtures/tox.ini

[tox]
envlist = py36,py37,py38,py39,py310,py311

[testenv]
passenv =
    XDG_CACHE_HOME
deps =
    six
    py
extras =
    dev
    full
commands =
    python -c 'import os, sys; print(os.path.realpath(sys.exec_prefix), "is the exec_prefix")'
Add very basic integration tests 2019-07-17 18:28:54 +02:00			`[tox]`
Drop tox < 3.24, add Python 3.11, fix tox 4 compatibility 2022-11-30 12:24:38 +01:00			`envlist = py36,py37,py38,py39,py310,py311`
Add very basic integration tests 2019-07-17 18:28:54 +02:00
			`[testenv]`
Avoid race conditions when running tests with xdist 2022-12-13 16:56:33 +01:00			`passenv =`
			`XDG_CACHE_HOME`
Add very basic integration tests 2019-07-17 18:28:54 +02:00			`deps =`
			`six`
			`py`
Add the --print-extras-to(-file) option 2020-09-11 15:20:03 +02:00			`extras =`
			`dev`
			`full`
Add very basic integration tests 2019-07-17 18:28:54 +02:00			`commands =`
tests: Use sys.exec_prefix, not sys.executable, to determine the Python run Virtualenv 20.0 follows symlinks when populating sys.executable, so we can't use it. (AFAIUI it's done to better handle cases where the system executable is changed after a virtualenv is created.) See: https://github.com/pypa/virtualenv/pull/1522 sys.exec_prefix still points to inside the virtualenv, so use that in the tests to determine what's being run. 2020-08-11 17:07:58 +02:00			`python -c 'import os, sys; print(os.path.realpath(sys.exec_prefix), "is the exec_prefix")'`