How to take into account ABI tag of a wheel : cp314-cp314t for an python 3.14t venv ?

[dir26738]

Hello,

I am playing with python 3.14t. I am on ubuntu 22.04, using pyenv to change the current python version. poetry is installed with python 3.11.14, and my project use python 3.14.0t.

I suspect that the ABI version is not take into account or I am doing something bad, not able to define the ABI.

Here is the project to play with :
poetry_abi_tag_isssue.zip

For me, with a wheel name like "numpy-2.3.4-cp314-cp314t-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl", the python version is cp314 and the abi version is cp314t.

As the active python is 3.14t (pyenv local 3.14.0t), I expect that poetry will use the wheel with abi tag "cp314t" and not the one this abi tag "cp314". When creating my env with the command "poetry sync --no-root", the result of "poetry env info" is :

pyenv local 3.14.0t
poetry sync --no-root
poetry env info

What I get in my venv :

Virtualenv
Python: 3.14.0
Implementation: CPython
Path: /home/xxx/PycharmProjects/poetry_abi_tag_isssue/.venv
Executable: /home/xxx/PycharmProjects/poetry_abi_tag_isssue/.venv/bin/python
Valid: True

Base
Platform: linux
OS: posix
Python: 3.14.0
Path: /home/xxx/.pyenv/versions/3.14.0t
Executable: /home/xxx/.pyenv/versions/3.14.0t/bin/python3.14

The virtual env is using python 3.14t exe, but here is the issue :

cat .venv/lib/python3.14t/site-packages/numpy-2.3.4.dist-info/WHEEL 

Wheel-Version: 1.0
Generator: meson
Root-Is-Purelib: false
Tag: cp314-cp314-manylinux_2_27_x86_64
Tag: cp314-cp314-manylinux_2_28_x86_64

AND

ls -l .venv/lib/python3.14**t**/site-packages/numpy/random/*.so

.venv/lib/python3.14t/site-packages/numpy/random/bit_generator.cpython-314-x86_64-linux-gnu.so

In my venv, the wrong wheel was used, I expected to see cpython-314t.so file only.

• How to solve it : ###

If poetry is installed while python 3.14t is activated, I have the correct wheel installed in my env :

cd
pyenv local 3.14.0t
curl -sSL https://install.python-poetry.org | python3 - --uninstall
curl -sSL https://install.python-poetry.org | python3 -
cd <py project>
rm -Rf .venv
pyenv local 3.14.0t
poetry sync --no-root

cat .venv/lib/python3.14t/site-packages/numpy-2.3.4.dist-info/WHEEL 

Wheel-Version: 1.0
Generator: meson
Root-Is-Purelib: false
Tag: cp314-cp314t-manylinux_2_27_x86_64
Tag: cp314-cp314t-manylinux_2_28_x86_64

AND

ls -l .venv/lib/python3.14**t**/site-packages/numpy/random/*.so

.venv/lib/python3.14t/site-packages/numpy/random/bit_generator.cpython-314t-x86_64-linux-gnu.so

Sorry to be so long, so my question :
I search for any questions about the ABI tag, I found no answer.

Is it supported ? --> I would say "yes", as it is working if poetry is installed with python 3.14t.

As poetry is marked to support python version per project, is it an issue ? Or how to set the ABI version.

Thanks for your support.

[radoering]

Thanks for the detailed report.

As poetry is marked to support python version per project, is it an issue ?

Yes, I think the issue is that Poetry does not distinguish between free-threaded and not free-threaded.

We probably have to fix get_supported_tags. #10361 fixes a similar issue.

[dir26738]

should i transform this question to a bug ?

[radoering]

Yeah, feel free to do so.

[dir26738]

I use latest poetry version, 2.2.1, so unfortunately #10361 will not help.
I look a little in get_supported_tags, sorry I am a bit lost. I just write a small test to have more info :

def test_sysconfig():
    from packaging.tags import cpython_tags
    import sysconfig
    from sys import version_info

    print(version_info)
    python = version_info[:3]

    print(f"ABIFLAGS={sysconfig.get_config_vars()['ABIFLAGS']}")
    print(f"ABI_THREAD={sysconfig.get_config_vars()['ABI_THREAD']}")


    tags = cpython_tags(python, platforms=None)

    for tag in tags:
        print(tag)

with the result (same if using poetry installed with 3.14.0 or 3.14.0t) :

sys.version_info(major=3, minor=14, micro=0, releaselevel='final', serial=0)
ABIFLAGS=t
ABI_THREAD=t
cp314-cp314t-manylinux_2_35_x86_64
cp314-cp314t-manylinux_2_34_x86_64
cp314-cp314t-manylinux_2_33_x86_64
cp314-cp314t-manylinux_2_32_x86_64
cp314-cp314t-manylinux_2_31_x86_64
cp314-cp314t-manylinux_2_30_x86_64
...
cp314-cp314t-manylinux1_x86_64
cp314-cp314t-linux_x86_64
cp314-none-manylinux_2_35_x86_64
...
cp314-none-manylinux1_x86_64
cp314-none-linux_x86_64

Hope this could help.

[radoering]

I use latest poetry version, 2.2.1, so unfortunately #10361 will not help.

I did not expect it to solve the issue. I just meant that it fixed a similar issue.

with the result (same if using poetry installed with 3.14.0 or 3.14.0t) :

cpython_tags() gives the same result for 3.14 and 3.14t? That would be somewhat surprising.

[radoering]

@dir26738 The issue should be fixed with #10614. I would be glad if you can try it out. (See https://python-poetry.org/docs/#installing-with-pipx for how to install Poetry from a PR.)

[dir26738]

done. I reply directly in the PR. For me it works fine, I managed to install my pythonn 3.14.0t env with a poetry installed in python 3.10. Great !