The approach looks good 😁

@gaborbernat that's interesting. The readthedocs build is failing because it's installing tox-uv which is very unhappy with this change as it's a breaking API change (PythonInfo gained a new field and constructor parameter: free_threaded). I never thought of tox as an API only CLI, but I suppose especially with plugins in mind, I better should have 😜

Now the question is how to best proceed. WDYT? Give the attribute a default value? Accept breaking the API? Something else entirely?

Give the attribute a default value?

This 😊

I was about to pick this up again. Thanks for continuing. There was also another test I was about to adjust. Further, I wanted to discuss the fact that PythonInfo is a NamedTuple. So adding a field will break code that structurally unpacks it e.g., (impl, _, version, _, _, extra) = python_info. Up to you to decide how/whether to handle this API incompatibility. Lastly, I think the free_threaded info should also be included in the json log, but it's not yet (only in my local changes 😬 )

I wanted to discuss the fact that PythonInfo is a NamedTuple. So adding a field will break code that structurally unpacks it e.g., (impl, _, version, _, _, extra) = python_info. Up to you to decide how/whether to handle this API incompatibility.

Yeah made it a dataclass. I'm fine breaking unpacking here.

There was also another test I was about to adjust.

Feel free to put in a new PR if there's anything else we can improve. Thanks!

I am trying to use this, and noticed that if I do e.g. tox -e py313t-test on a machine that does not have free-threaded Python installed, the build still runs and silently uses the non-freethreaded version of Python. It might be worth making sure that py313t fails if a free-threaded Python interpreter cannot be found?

I am trying to use this, and noticed that if I do e.g. tox -e py313t-test on a machine that does not have free-threaded Python installed, the build still runs and silently uses the non-freethreaded version of Python. It might be worth making sure that py313t fails if a free-threaded Python interpreter cannot be found?

PR welcome 😁

@astrofrog I cannot reproduce the issue. Here's what I tried (inside a ubuntu:24.04 docker container)

export DEBIAN_FRONTEND=noninteractive
cd /root
apt update
apt install -y locales
localedef -i en_US -c -f UTF-8 -A /usr/share/locale/locale.alias en_US.UTF-8
export LANG=en_US.UTF-8
apt-get install -y --no-install-recommends build-essential libssl-dev zlib1g-dev libbz2-dev libreadline-dev libsqlite3-dev wget curl llvm libncurses5-dev xz-utils tk-dev libxml2-dev libxmlsec1-dev libffi-dev liblzma-dev ca-certificates vim git software-properties-common tar
curl -fsSL https://pyenv.run | bash
export PYENV_ROOT="$HOME/.pyenv"
[[ -d $PYENV_ROOT/bin ]] && export PATH="$PYENV_ROOT/bin:$PATH"
eval "$(pyenv init - bash)"
pyenv install 3.13
pyenv install 3.12
pyenv global 3.13 3.12
pyenv rehash
python3.12 -m pip install tox

mkdir -p /root/tmp
cd /root/tmp
cat << EOF > pyproject.toml
[project]
name = "foo"
version = "0.0.1"

[build-system]
requires = ["setuptools >= 77.0.3"]
build-backend = "setuptools.build_meta"

[tool.tox]
requires = ["tox>=4.26"]
env_list = ["py313-test"]

[tool.tox.env.py313-test]
commands = [
    ["python", "-VV"]
]
EOF

# works, prints "Python 3.13.4 (main, Jun  7 2025, 13:03:46) [GCC 13.3.0]"
python3.12 -m tox

sed -i 's/py313-test/py313t-test/' pyproject.toml
# fails as expected with "py313t: skipped because could not find python interpreter with spec(s): py313t"
python3.12 -m tox