Skip to content

Conversation

@wshanks
Copy link
Contributor

@wshanks wshanks commented Mar 4, 2025

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 the issue that led to the need to set the default runner has been addressed and that appears to be confirmed by testing.

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](fedora-python#42 (comment))
the issue that led to the need to set the default runner has been
addressed and that appears to be confirmed by testing.
@wshanks
Copy link
Contributor Author

wshanks commented Mar 4, 2025

I am not sure about the test failures but they seem unrelated to the changes here (problem setting up Python 3.7).

@hroncok
Copy link
Member

hroncok commented Mar 4, 2025

Do you mind if I add commits related to the CI problem to your PR?

@wshanks
Copy link
Contributor Author

wshanks commented Mar 4, 2025

Fine with me 🙂

@hroncok hroncok merged commit c656431 into fedora-python:master Mar 4, 2025
13 checks passed
@hroncok
Copy link
Member

hroncok commented Mar 4, 2025

Thank you.

Working on a followup release in #88

@wshanks wshanks deleted the default-env branch March 4, 2025 23:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants