-
Notifications
You must be signed in to change notification settings - Fork 179
Support Python 3.14 #1108
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
base: master
Are you sure you want to change the base?
Support Python 3.14 #1108
Conversation
|
@maartenbreddels I don't have time to debug this further. #1107 is fixed, but #1109 isn't yet. Feel free to work further on this PR branch, or merge it. I would highly recommend prioritizing this, since Python 3.14 stable is already released. For next year, I recommend using the release candidate period to find such bugs in new Python versions. For Python 3.15, this period starts July 28th, 2026. |
|
@maartenbreddels any chance you or someone from your team can work on Python 3.14 support? |
|
Integration tests are failing locally with: This is an indication that we are a bit early with 3.14 support. Unittests are passing locally. |
a1ee879 to
867f670
Compare
|
We'll have to wait for a 3.14 release from altair I think vega/altair#3895 |
|
windows failure on 3.14: Not sure why this is experimental |
|
Ah yes, i'm all for integrating the fixes, before officially "supporting 3.14". |
|
Done, see #1123. |
|
altair 6.0.0 Is now released with Python 3.14 support. |
|
Any update on Python 3.14 support? |
|
Since this PR is not moving forward, shall I close it? |
|
No, why close it? |
Support Python 3.14.
Work in progress
Closes #1107.