-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
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
BUG: Cannot import pandas2.2.3 in free-threading python3.13.0 #60224
Comments
cc @lithomas1 |
That's true, although in practice this was only tested on Linux and MacOS, because at that time numpy only did have free-threading support for those platforms (at least only wheels for those platforms). So we also didn't provide windows wheels with free-threading support.
That's not a wheel that pandas provided (https://pypi.org/project/pandas/2.2.3/#files), so did you build that yourself locally? NumPy recently started providing free-threaded wheels for Windows, and so now pandas will also be able to test Windows support. @lysnikolaou started doing that in #60146, although I don't see any code changed that were required to get it running, which should suggest that also pandas 2.2.3 already worked on Windows. |
Correct, no free-threading Windows binaries were uploaded yet. I agree with Joris that the downloaded wheel looks suspicious. |
I deleted this wheel file and noticed
Thanks for the information. That's a big help. |
UPDATE: |
@shinyano Thanks for testing! That's good to hear it is working |
Pandas version checks
Reproducible Example
Issue Description
According to release note, pandas2.2.3 can be used in free-threading python. But when importing pandas(2.2.3) in python3.13t on windows11, python would exit without output or error message:
Then I built cpython with debug flag and tried again, the output is as follows:
Expected Behavior
Pandas should be correctly imported.
Installed Versions
I can't use pandas in python3.13t, so it's a little hard to execute
pd.show_versions()
.The text was updated successfully, but these errors were encountered: