Python 3.13.9: What You Need to Know About This Urgent Bug Fix Release

Python 3.13.9 is here as a quick, targeted update to address a regression that slipped into the previous release. In this Q&A, we break down the key details—why this version was expedited, the exact bug it fixes, and how you can get it. Whether you’re a developer, system administrator, or Python enthusiast, this guide covers everything you need to know about this patch.

What is Python 3.13.9 and why was it released so quickly?

Python 3.13.9 is an expedited release of the Python language, meaning it was pushed out faster than a typical minor update. The sole purpose of this version is to fix a critical regression that appeared in Python 3.13.8. Regressions are bugs introduced in a new release that break functionality that previously worked correctly. Because this regression impacted a commonly used introspection tool, the Python release team decided to issue a rapid fix to restore stability. Think of it as a hotfix: no new features, no other changes—just a focused correction to keep Python reliable for all users. The expedited process ensures that developers and systems relying on the affected functionality can quickly get back to normal without waiting for a larger, scheduled release.

What specific bug does Python 3.13.9 fix?

This release patches a single issue: gh-139783, a regression in the inspect module. Specifically, the bug affected the inspect.getsourcelines() function when a decorator was followed by a comment or an empty line before the decorated function definition. In Python 3.13.8, calling get_sourcelines() in such cases would raise an error or return incorrect results, breaking code that relies on source inspection—for example, debugging tools, test frameworks, or documentation generators. The fix ensures that getsourcelines() correctly handles these edge cases, restoring its ability to locate and return source lines even when comments or blank lines appear between a decorator and its function. This was the only regression addressed, making 3.13.9 a straightforward upgrade for anyone affected by this issue.

Were there any other changes in Python 3.13.9 compared to 3.13.8?

No, there are no other changes in Python 3.13.9 beyond the bug fix described above. The release notes explicitly state that this is a minimal patch release containing only the correction for gh-139783. This means you can upgrade from 3.13.8 to 3.13.9 with confidence that no new features, deprecations, or behavioral changes have been introduced. The Python release team deliberately kept the scope narrow to ensure the fix could be delivered quickly and safely. If you were already using Python 3.13.8 and the regression didn’t affect you, you may choose to stay on that version—but upgrading is recommended to keep your environment consistent with the latest stable patch.

How can I download and install Python 3.13.9?

You can download Python 3.13.9 from the official Python website at python.org/downloads/release/python-3139/. The page offers installers for Windows, macOS, and Linux (source code). If you’re using a package manager like apt, brew, or pyenv, the update may appear shortly after the official release. For Python developers using virtual environments, simply running python3.13 -m pip install --upgrade pip or reinstalling Python 3.13.9 will ensure your environment is up to date. Always verify your installation by running python --version after upgrading. Remember to back up any critical projects before switching patch versions, though the change is minimal.

Who is responsible for this release and how can I support Python development?

This release was managed by the Python Release Team, including Thomas Wouters, Ned Deily, Steve Dower, and Łukasz Langa. They coordinated the expedited process alongside countless volunteers in the Python community. The Python Software Foundation (PSF) oversees these efforts and relies on contributions to fund infrastructure, events, and development. You can support Python by volunteering your time—for example, triaging issues on the bug tracker, writing documentation, or improving the CPython codebase. Organisations can also contribute financially to the PSF. Every bit of help ensures Python remains free, open-source, and well-maintained. To get involved, visit the PSF website or the official CPython repository on GitHub. Your support makes releases like 3.13.9 possible.

Where can I find more resources and report issues for Python 3.13.9?

For detailed information about Python 3.13.9, check out the following resources:

• Official 3.13 Documentation – Complete API reference and tutorials.
• PEP 745 – The release schedule and process for Python 3.13.
• Bug Tracker – Report issues or view existing ones on GitHub.
• Python Software Foundation – Support Python development with a donation.

If you encounter any new bugs in 3.13.9, please submit them to the CPython issue tracker. The community appreciates your help in making Python better for everyone. Enjoy the release!