From b73cf22d7360bd1d60a586b3ba39cc5f8017de0b Mon Sep 17 00:00:00 2001 From: Will Shanks Date: Tue, 4 Mar 2025 14:10:44 -0500 Subject: [PATCH] Avoid setting the default runner Setting the default runner to tox's default when `--current-env` is not used can override another plugin like `tox-uv` which wants to change the default runner. According to [this comment](https://github.com/fedora-python/tox-current-env/pull/42#discussion_r1048595612) the issue that led to the need to set the default runner has been addressed and that appears to be confirmed by testing. --- src/tox_current_env/hooks4.py | 4 ---- 1 file changed, 4 deletions(-) diff --git a/src/tox_current_env/hooks4.py b/src/tox_current_env/hooks4.py index 9c0f003..7597cca 100644 --- a/src/tox_current_env/hooks4.py +++ b/src/tox_current_env/hooks4.py @@ -93,10 +93,6 @@ def tox_add_core_config(core_conf, state): opt.default_runner = "print-env" return - # No options used - switch back to the standard runner - # Workaround for: https://github.com/tox-dev/tox/issues/2264 - opt.default_runner = "virtualenv" - @impl def tox_add_env_config(env_conf, state):