Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TOXENV=py313t doesn't work #3467

Closed
ngoldbaum opened this issue Jan 16, 2025 · 1 comment
Closed

TOXENV=py313t doesn't work #3467

ngoldbaum opened this issue Jan 16, 2025 · 1 comment

Comments

@ngoldbaum
Copy link

ngoldbaum commented Jan 16, 2025

Issue

Now that virtualenv has support for free-threaded Python, tox should also add support for environment names like py313t. The virtualenv release came out in the last 24 hours and that led to CI breakage on bcrypt, which was testing free-threaded python using tox.

Environment

See e.g. this CI run: https://github.com/pyca/bcrypt/actions/runs/12814705768/job/35731757807?pr=953

In that run TOXENV is set to py313t. I had it set to py313 before the last virtualenv release, which worked, to work around the lack of support in virtualenv.

Output of running tox

Output of tox -rvv
ROOT: 209 E HandledError| provided environments not found in configuration file:
cp313t [tox/run.py:23]

Minimal example

Clone the bcrypt repo and run tox with a free-threaded python installed and TOXENV set to py313t. You'll need a rust toolchain installed.

@gaborbernat
Copy link
Member

Duplicate of #3391

@gaborbernat gaborbernat marked this as a duplicate of #3391 Jan 16, 2025
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

No branches or pull requests

2 participants