github.com_fedora-python_tox-current-env

mirrors/github.com_fedora-python_tox-current-env

Fork 0

mirror of https://github.com/fedora-python/tox-current-env.git synced 2025-01-12 17:26:14 +01:00

Commit Graph

Author	SHA1	Message	Date
Petr Viktorin	2e513fe88f	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
Miro Hrončok	783c2ea1ec	Tests: For each test function, create an isolated project directory This allows concurrent test execution. Fixes https://github.com/fedora-python/tox-current-env/issues/11	2019-10-23 13:24:51 +02:00

Author

SHA1

Message

Date

Petr Viktorin

2e513fe88f

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

Miro Hrončok

783c2ea1ec

Tests: For each test function, create an isolated project directory

This allows concurrent test execution.

Fixes https://github.com/fedora-python/tox-current-env/issues/11

2019-10-23 13:24:51 +02:00

2 Commits