-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Run tests on Python 3.14 #13138
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
Run tests on Python 3.14 #13138
Conversation
Seems like most the failures on 3.14 are related to the number of |
|
pip/src/pip/_internal/utils/urls.py Line 15 in ffbf6f0
|
Seems more changes (python/cpython#126679) are likely to the output of |
Would it make sense to skip the failing test on Python 3.14 until Python 3.14 beta 1? |
If another maintainer wants to do this I would be supportive. But I’m not volunteering to do so, as it would require a commitment to both turn on and fix those tests in a timely manner, and I can’t guarantee I will remember or have the time when needed. I don't want us to have the illusion that Python 3.14 is green when there are known issues with the test suite. |
Python 3.14 is now in beta so it's worth testing pip again. I'm sure all of the URI tests will need to be updated (again) but otherwise, let's see what else is broken! |
@ichard26 FYI I won't have time to work on this for at least a few weeks. Feel free to take over this PR or make a new one if you were interested in fixing 3.14 tests. |
This PR is to run tests for Python 3.14, but not to explicitly support Python 3.14.
I think the earlier we add this the better, as if there's some breaking change in 3.14 that we think shouldn't be breaking it might need to be reported before the CPython beta (i.e. feature freeze).
However, I'm just leaving this as draft for now until I know if there is non-trivial work to do to pass the tests on 3.14.