-
-
Notifications
You must be signed in to change notification settings - Fork 279
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
propagate abiflags to wheel name on Windows #2325
Conversation
For what it's worth, I verified with Also, https://pypi.org/project/numpy/#numpy-2.1.3-cp313-cp313-win_amd64.whl |
@ngoldbaum any idea about the 3.13t failure? Looks like a |
I reported it over at Quansight-Labs/setup-python#4. I honestly have no idea what changed on the runners. |
never mind, the python.org ftp fell over: python/pythondotorg#2663 |
I also hit this over on rpds-py: https://github.com/ngoldbaum/rpds/actions/runs/12041384455/job/33573211395#step:4:137 The issue with python.org is fixed so I think if you restart CI it will at least get past installing python. |
I pushed an additional commit which should hopefully fix the test failures. I was looking in The two seem to always be equivalent on unix platforms, so I think we're fine to switch to lower-case Result of grepping sysconfig directory
|
Ok will debug more later... |
Ok, I take it back. The
... I've pushed a commit which manually encodes the expected flags. |
Seems like the wheel tag is still wrong for abi3 on Windows when building for 3.13t:
https://github.com/messense/nh3/actions/runs/12069973856/job/33658408634#step:6:32 |
Agh thanks for flagging, I can try to investigate tonight if you don't get there first :) |
So the problem is that windows abi3 wheel currently doesn't not resolve python interpreter correctly for 3.13t, see Lines 372 to 391 in 57c74b6
and Lines 401 to 418 in 57c74b6
these hacks work fine before but fell short with 3.13t. I'm off to sleep now, feel free to investigate further. |
This is an attempt to fix #2325 (comment) (Not tested yet, I wanted to push and see how this runs on CI as well as test locally.) --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
xref pydantic/jiter#172 (comment)
At the moment the windows builds are hard coded to use the
none
abi tag (unless they are abi3). I think this is probably technically incorrect, though in practice has worked fine historically because there was only one build on Windows... until 3.13t has come along with free-threading as a second option :)It's important that we do emit proper abi tags (e.g.
cp313
,cp313t
) because otherwise the two 3.13 wheels end up with the same name and can't be uploaded to PyPI. I think I also saw some install failures onjiter
CI where a Python 3.13 build ended up installing the other build's wheel (I thinkpip
detected an incorrect lib name and rejected it).I suspect I might need to fix some tests...