Python 3.9.13 is now available

OpenTeams May 17, 2022

 

This is the thirteenth maintenance release of Python 3.9. Get it here:
Python 3.9.13

According to the release calendar specified in PEP 596, Python 3.9.13 is the final
regular maintenance release. Starting now, the 3.9 branch will only
accept security fixes and releases of those will be made in source-only
form until October 2025.

This is a milestone moment for me as it means that now both of my
release series are security-only. My work as release manager enters its
final stage. I’m not crying, you’re crying! :smiling_face_with_tear:

Compared to the 3.8 series, this last regular bugfix release is still
pretty active at 166 commits since 3.9.12. In comparison, version
3.8.10, the final regular bugfix release of Python 3.8, included only 92
commits. However, it’s likely that it was 3.8 that was special here
with the governance changes occupying core developers’ minds. For
reference, version 3.7.8, the final regular bugfix release of Python
3.7, included 187 commits.

In any case, 166 commits is quite a few changes, some of which being pretty important fixes. Take a look at the change log for details.

Major new features of the 3.9 series, compared to 3.8

Some of the new major new features and changes in Python 3.9 are:

  • PEP 573, Module State Access from C Extension Methods
  • PEP 584, Union Operators in dict
  • PEP 585, Type Hinting Generics In Standard Collections
  • PEP 593, Flexible function and variable annotations
  • PEP 602, Python adopts a stable annual release cadence
  • PEP 614, Relaxing Grammar Restrictions On Decorators
  • PEP 615, Support for the IANA Time Zone Database in the Standard Library
  • PEP 616, String methods to remove prefixes and suffixes
  • PEP 617, New PEG parser for CPython
  • BPO 38379, garbage collection does not block on resurrected objects;
  • BPO 38692, os.pidfd_open added that allows process management without races and signals;
  • BPO 39926, Unicode support updated to version 13.0.0;
  • BPO 1635741, when Python is initialized multiple times in the same process, it does not leak memory anymore;
  • A number of Python builtins (range, tuple, set, frozenset, list, dict) are now sped up using PEP 590 vectorcall;
  • A number of Python modules (_abc, audioop, _bz2, _codecs,
    _contextvars, _crypt, _functools, _json, _locale, operator, resource,
    time, _weakref) now use multiphase initialization as defined by PEP 489;
  • A number of standard library modules (audioop, ast, grp, _hashlib,
    pwd, _posixsubprocess, random, select, struct, termios, zlib) are now
    using the stable ABI defined by PEP 384.

You can find a more comprehensive list in this release’s “What’s New” document.

We hope you enjoy Python 3.9!

Thanks to all of the many volunteers who help make Python Development
and these releases possible! Please consider supporting our efforts by
volunteering yourself or through organization contributions to the
Python Software Foundation.

Your friendly release team,
Ned Deily @nad
Steve Dower @steve.dower
Łukasz Langa @ambv

Categories: Uncategorized
Tags:

Related Articles

Python 3.10.5 is available

The latest bugfix drop for Python 3.10 is here: Python 3.10.5. This release packs more than 230 bugfixes and docs changes, so you surely want to update 🙂 You can get it here:https://www.python.org/downloads/release/python-3105/This is the first maintenance release of Python 3.10Python 3.10.5 is the newest major release of the Python programming language, and it contains many new features and optimizations.Major new features of the 3.10 series, compared to 3.9Among the new major new features and changes so far:PEP 623 – Deprecate and prepare for the removal of the wstr member in PyUnicodeObject.PEP 604 – Allow writing union types as X | YPEP 612 – Parameter Specification VariablesPEP 626 – Precise line numbers for debugging and other tools.PEP 618 – Add Optional Length-Checking To zip.bpo-12782: Parenthesized context managers are now officially allowed.PEP 632 – Deprecate distutils module.PEP 613 – Explicit Type AliasesPEP 634 – Structural Pattern Matching: SpecificationPEP 635 – Structural Pattern Matching: Motivation and RationalePEP 636 – Structural Pattern Matching: TutorialPEP 644 – Require OpenSSL 1.1.1 or newerPEP 624 – Remove Py_UNICODE encoder APIsPEP 597 – Add optional EncodingWarningMore resourcesOnline DocumentationPEP 619, 3.10 Release ScheduleReport bugs at https://bugs.python.org.Help fund Python and its community.bpo-38605: from __future__ import annotations (PEP 563) used to be on this list in previous pre-releases but it has been postponed to Python 3.11 due to some compatibility concerns. You can read the Steering Council communication about it here to learn more.And now for something completely differentStrange quarks are the third lightest quarks, which are subatomic particles that are so small,  they are believed to be the fundamental particles, and not further divisible. Like down quarks, strange quarks have a charge of -1/3. Like all fermions (which are particles that can not exist in the same place at the same time), strange quarks have a spin of 1/2. What makes strange quarks different from down quarks–apart from having 25 times the mass of down quarks–is that they have something that scientists call “strangeness.” Strangeness is basically a resistance to decay against strong force and electromagnetism. This means that any particle that contains a strange quark can not decay due to strong force (or electromagnetism), but instead with the much slower weak force. It was believed that this was a ‘strange’ method of decay, which is why the scientists gave the particles that name.We hope you enjoy the new releases!Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organization contributions to the Python Software Foundation.https://www.python.org/psf/Your friendly release team,Ned Deily @nad Steve Dower @steve.dower Pablo Galindo Salgado @pablogsal

OpenTeams June 6, 2022

Python 3.10.6 is available

Here you have a nice package of 200 commits of bugfixes and documentation improvements freshly made for Python 3.10. Go and download it when is still hot:https://www.python.org/downloads/release/python-3106/This is the sixth maintenance release of Python 3.10Python 3.10.6 is the newest major release of the Python programming language, and it contains many new features and optimizations.Major new features of the 3.10 series, compared to 3.9Among the new major new features and changes so far:PEP 623 – Deprecate and prepare for the removal of the wstr member in PyUnicodeObject.PEP 604 – Allow writing union types as X | YPEP 612 – Parameter Specification VariablesPEP 626 – Precise line numbers for debugging and other tools.PEP 618 – Add Optional Length-Checking To zip.bpo-12782: Parenthesized context managers are now officially allowed.PEP 632 – Deprecate distutils module.PEP 613 – Explicit Type AliasesPEP 634 – Structural Pattern Matching: SpecificationPEP 635 – Structural Pattern Matching: Motivation and RationalePEP 636 – Structural Pattern Matching: TutorialPEP 644 – Require OpenSSL 1.1.1 or newerPEP 624 – Remove Py_UNICODE encoder APIsPEP 597 – Add optional EncodingWarningMore resourcesOnline DocumentationPEP 619, 3.10 Release ScheduleReport bugs at https://bugs.python.org.Help fund Python and its community.bpo-38605: from __future__ import annotations (PEP 563) used to be on this list in previous pre-releases but it has been postponed to Python 3.11 due to some compatibility concerns. You can read the Steering Council communication about it here to learn more.And now for something completely differentA pentaquark is a human-made subatomic particle, consisting of four quarks and one antiquark bound together; they are not known to occur naturally or exist outside of experiments to create them. As quarks have a baryon number of (+1/3), and antiquarks of (−1/3), the pentaquark would have a total baryon number of 1 and thus would be a baryon. Further, because it has five quarks instead of the usual three found in regular baryons (a.k.a. ‘triquarks’), it is classified as an exotic baryon. The name pentaquark was coined by Claude Gignoux et al. (1987) and Harry J. Lipkin in 1987; however, the possibility of five-quark particles was identified as early as 1964 when Murray Gell-Mann first postulated the existence of quarks. Although predicted for decades, pentaquarks proved surprisingly tricky to discover and some physicists were beginning to suspect that an unknown law of nature prevented their production.We hope you enjoy the new releases!Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organization contributions to the Python Software Foundation.https://www.python.org/psf/Your friendly release team,Ned Deily @nad Steve Dower @steve.dower Pablo Galindo Salgado @pablogsal

OpenTeams August 2, 2022

Python 3.12.0 release candidate 3 now available

 I’m pleased to announce the release of Python 3.12 release candidate 3.https://www.python.org/downloads/release/python-3120rc3/ This is the second release candidate of Python 3.12.0This release, 3.12.0rc3, is the absolutely last release preview for Python 3.12.
There will be no ABI changes from this point forward
in the 3.12 series. The intent is for the final release of 3.12.0,
scheduled for Monday, 2023-10-02, to be identical to this release
candidate. This really is the last chance to find critical problems in Python 3.12.Call to action
We strongly encourage maintainers of third-party Python projects to
prepare their projects for 3.12 compatibilities during this phase, and
where necessary publish Python 3.12 wheels on PyPI to be ready for the
final release of 3.12.0. Any binary wheels built against Python
3.12.0rc3 will work with future versions of Python 3.12. As always,
report any issues to the Python bug tracker.
Please keep in mind that this is a preview release and while it’s as close to the final release as we can get it, its use is not recommended for production environments.
Core developers: time to work on documentation now
Are all your changes properly documented?Are they mentioned in What’s New?Did you notice other changes you know of to have insufficient documentation?
 Major new features of the 3.12 series, compared to 3.11
 New features
More flexible f-string parsing, allowing many things previously disallowed (PEP 701).Support for the buffer protocol in Python code (PEP 688).A new debugging/profiling API (PEP 669).Support for isolated subinterpreters with separate Global Interpreter Locks (PEP 684).Even more improved error messages. More exceptions potentially caused by typos now make suggestions to the user.Support for the Linux perf profiler to report Python function names in traces.Many large and small performance improvements (like PEP 709 and support for the BOLT binary optimizer), delivering an estimated 5% overall performance improvementcitation needed.
Type annotations
New type annotation syntax for generic classes (PEP 695).New override decorator for methods (PEP 698).
Deprecations
The deprecated wstr and wstr_length members of the C implementation of unicode objects were removed, per PEP 623.In the unittest module, a number of long deprecated methods and classes were removed. (They had been deprecated since Python 3.1 or 3.2).The deprecated smtpd and distutils modules have been removed (see PEP 594 and PEP 632. The setuptools package continues to provide the distutils module.A number of other old, broken and deprecated functions, classes and methods have been removed.Invalid backslash escape sequences in strings now warn with SyntaxWarning instead of DeprecationWarning, making them more visible. (They will become syntax errors in the future.)The internal representation of integers has changed in preparation
for performance enhancements. (This should not affect most users as it
is an internal detail, but it may cause problems for Cython-generated
code.)
(Hey, fellow core developer, if a feature you find important is missing from this list, let Thomas know.)
For more details on the changes to Python 3.12, see What’s new in Python 3.12. The next scheduled release of Python 3.12 will be 3.12.0, the final release, currently scheduled for 2023-10-02.
 More resources
Online Documentation.PEP 693, the Python 3.12 Release Schedule.Report bugs via GitHub Issues.Help fund Python and its community. Enjoy the new releaseThanks
to all of the many volunteers who help make Python Development and
these releases possible! Please consider supporting our efforts by
volunteering yourself or through organization contributions to the Python Software Foundation.Your release team,Thomas WoutersNed DeilySteve DowerŁukasz Langa

OpenTeams September 19, 2023

Python 3.12.0 release candidate 2 now available

I’m pleased to announce the release of Python 3.12 release candidate 2.https://www.python.org/downloads/release/python-3120rc2/ This is the second release candidate of Python 3.12.0This release, 3.12.0rc2, is the last release preview for Python 3.12.
There will be no ABI changes from this point forward
in the 3.12 series. The intent is for the final release of 3.12.0,
scheduled for Monday, 2023-10-02, to be identical to this release
candidate. This is the last chance to find critical problems in Python 3.12.Call to action
We strongly encourage maintainers of third-party Python projects to
prepare their projects for 3.12 compatibilities during this phase, and
where necessary publish Python 3.12 wheels on PyPI to be ready for the
final release of 3.12.0. Any binary wheels built against Python
3.12.0rc2 will work with future versions of Python 3.12. As always,
report any issues to the Python bug tracker.
Please keep in mind that this is a preview release and while it’s as close to the final release as we can get it, its use is not recommended for production environments.
Core developers: time to work on documentation now
Are all your changes properly documented?Are they mentioned in What’s New?Did you notice other changes you know of to have insufficient documentation?
 Major new features of the 3.12 series, compared to 3.11
 New features
More flexible f-string parsing, allowing many things previously disallowed (PEP 701).Support for the buffer protocol in Python code (PEP 688).A new debugging/profiling API (PEP 669).Support for isolated subinterpreters with separate Global Interpreter Locks (PEP 684).Even more improved error messages. More exceptions potentially caused by typos now make suggestions to the user.Support for the Linux perf profiler to report Python function names in traces.Many large and small performance improvements (like PEP 709), delivering an estimated 5% overall performance improvementcitation needed.
Type annotations
New type annotation syntax for generic classes (PEP 695).New override decorator for methods (PEP 698).
Deprecations
The deprecated wstr and wstr_length members of the C implementation of unicode objects were removed, per PEP 623.In the unittest module, a number of long deprecated methods and classes were removed. (They had been deprecated since Python 3.1 or 3.2).The deprecated smtpd and distutils modules have been removed (see PEP 594 and PEP 632. The setuptools package continues to provide the distutils module.A number of other old, broken and deprecated functions, classes and methods have been removed.Invalid backslash escape sequences in strings now warn with SyntaxWarning instead of DeprecationWarning, making them more visible. (They will become syntax errors in the future.)The internal representation of integers has changed in preparation
for performance enhancements. (This should not affect most users as it
is an internal detail, but it may cause problems for Cython-generated
code.)
(Hey, fellow core developer, if a feature you find important is missing from this list, let Thomas know.)
For more details on the changes to Python 3.12, see What’s new in Python 3.12. The next scheduled release of Python 3.12 will be 3.12.0, the final release, currently scheduled for 2023-10-02.
 More resources
Online Documentation.PEP 693, the Python 3.12 Release Schedule.Report bugs via GitHub Issues.Help fund Python and its community. Enjoy the new releaseThanks
to all of the many volunteers who help make Python Development and
these releases possible! Please consider supporting our efforts by
volunteering yourself or through organization contributions to the Python Software Foundation.Your release team,Thomas WoutersNed DeilySteve DowerŁukasz Langa

OpenTeams September 6, 2023

Python 3.12.0 release candidate 1 released

  I’m pleased to announce the release of Python 3.12 release candidate 1.https://www.python.org/downloads/release/python-3120rc1/This is the first release candidate of Python 3.12.0
This release, 3.12.0rc1, is the penultimate release
preview. Entering the release candidate phase, only reviewed code
changes which are clear bug fixes are allowed between this release
candidate and the final release. The second candidate (and the last
planned release preview) is scheduled for Monday, 2023-09-04, while the
official release of 3.12.0 is scheduled for Monday, 2023-10-02.
There will be no ABI changes from this point forward in the 3.12 series, and the goal is that there will be as few code changes as possible.
Call to action
We strongly encourage maintainers of third-party Python projects to
prepare their projects for 3.12 compatibilities during this phase, and
where necessary publish Python 3.12 wheels on PyPI to be ready for the
final release of 3.12.0. Any binary wheels built against Python
3.12.0rc1 will work with future versions of Python 3.12. As always,
report any issues to the Python bug tracker.
Please keep in mind that this is a preview release and while it’s as close to the final release as we can get it, its use is not recommended for production environments.
Core developers: time to work on documentation now
Are all your changes properly documented?Are they mentioned in What’s New?Did you notice other changes you know of to have insufficient documentation?
Major new features of the 3.12 series, compared to 3.11
New features
More flexible f-string parsing, allowing many things previously disallowed (PEP 701).Support for the buffer protocol in Python code (PEP 688).A new debugging/profiling API (PEP 669).Support for isolated subinterpreters with separate Global Interpreter Locks (PEP 684).Even more improved error messages. More exceptions potentially caused by typos now make suggestions to the user.Support for the Linux perf profiler to report Python function names in traces.Many large and small performance improvements (like PEP 709), delivering an estimated 5% overall performance improvementcitation needed.
Type annotations
New type annotation syntax for generic classes (PEP 695).New override decorator for methods (PEP 698).
Deprecations
The deprecated wstr and wstr_length members of the C implementation of unicode objects were removed, per PEP 623.In the unittest module, a number of long deprecated methods and classes were removed. (They had been deprecated since Python 3.1 or 3.2).The deprecated smtpd and distutils modules have been removed (see PEP 594 and PEP 632. The setuptools package continues to provide the distutils module.A number of other old, broken and deprecated functions, classes and methods have been removed.Invalid backslash escape sequences in strings now warn with SyntaxWarning instead of DeprecationWarning, making them more visible. (They will become syntax errors in the future.)The internal representation of integers has changed in preparation
for performance enhancements. (This should not affect most users as it
is an internal detail, but it may cause problems for Cython-generated
code.)
(Hey, fellow core developer, if a feature you find important is missing from this list, let Thomas know.)
For more details on the changes to Python 3.12, see What’s new in Python 3.12. The next pre-release of Python 3.12 will be 3.12.0rc2, the final release candidate, currently scheduled for 2023-09-04.
More resources
Online Documentation.PEP 693, the Python 3.12 Release Schedule.Report bugs via GitHub Issues.Help fund Python and its community.Enjoy the new releaseThanks
to all of the many volunteers who help make Python Development and
these releases possible! Please consider supporting our efforts by
volunteering yourself or through organization contributions to the Python Software Foundation.Your release team,Thomas WoutersNed DeilySteve DowerŁukasz Langa

OpenTeams August 6, 2023

OpenTeams bridges the gap between enterprises and the open source community, facilitating adoption and optimization of open source technologies. By fostering trust and enhancing communication, OpenTeams enables companies to leverage the full potential of open source solutions, driving innovation and efficiency in the enterprise.

Twitter Facebook Youtube Linkedin Envelope
Resources
Company

© 2024 OpenTeams. All Rights Reserved.