-
-
Notifications
You must be signed in to change notification settings - Fork 842
Update to python 3.13 #18591
Copy link
Copy link
Closed
Labels
merge-earlyMerge Early in a developer cycleMerge Early in a developer cyclep5https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Milestone
Description
Activity
Metadata
Metadata
Assignees
Labels
merge-earlyMerge Early in a developer cycleMerge Early in a developer cyclep5https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Related issues, PRs or discussions
None
What is the current state of the codebase?
We have been stuck on python 3.11 due to a bug in py2exe which is now fixed (context: #18449).
We should now be able to update safely to Python 3.13.
Note: Python 3.13 has limited support for Windows 8.1.
We will drop 8.1 support with this upgrade.
python/cpython#98383
Why are changes required?
We need to keep up with the latest python version for security and general reasons
What technical changes are required?
Updating dependencies and python version specifiers in the build system.
actions/setup-python@v5from stepsAre the proposed technical changes API breaking?
Yes
Are there potential risks or issues with the proposed implementation?
Yes, we should perform this early in the 2026.1 release cycle