-
Notifications
You must be signed in to change notification settings - Fork 280
Plan to support free-threaded Python #1555
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Yes, I was testing PyO3 0.23 (when it was just a git branch) in #1450 and plan to proceed further with that upgrade this week. There is potentially additional work required beyond your list to actually make free-threaded support ok, both here and in |
PyO3 has now been bumped but there's a build failure on aarch64 on |
@sydney-runkle @Viicos this should go on the TODO list for Pydantic 2.11. |
For what it's worth, the build failures are fixed so we could move forward here in core relatively quickly. I fear that upstream pydantic is likely to be harder due to caches. |
We merged a test run in #1626, which is the first step. Build still fails, so fixing that will need to happen next. |
After #1628 the free-threaded test suite is all happy except for assertions dependent on The work will now be in |
In free-threaded build, importing
pydantic_core
currently results in a segmentation fault. PyO3 v0.23 introduces support for free-threaded Python and addresses this issue. Is there any short-term plan to migrate to PyO3 0.23?Currently I see the following blockers:
SerializationCallable
Sync
, which isn't because ofCollectWarnings
andSerRecursionState
containRefCells
IntoPy
/ToPyObject
byIntoPyObject
*_bound
methods,into_py
/to_object
)The text was updated successfully, but these errors were encountered: