python-committers July 2022

python-committers@python.org

2 participants
5 discussions

[RELEASE] The last 3.11 beta release (3.11.0b5) is now available
by Pablo Galindo Salgado 26 Jul '22

26 Jul '22

Here we are. The universe. The vastness of spacetime. At the edge. The last frontier. The last beta*(conditions apply) for Python 3.11. We have defied the powerful gods of release blockers and we have won by using the required amount of ruse and subterfuge. https://www.python.org/downloads/release/python-3110b5/ ## :warning: PLEASE HELP US TO TEST THIS RELEASE :warning: Due to the modified release schedule and the stability concerns regarding the past beta releases, please, please, please, please, help us to test Python 3.11 by testing this beta releases. * if you maintain a library or a third-party package. Test the beta releases! * If you have code that you maintain at work/research centre/classroom/whatever. Test the beta releases! * If you are a multi-million corporation that uses Python. Test the beta releases! * If you are a single-person company that uses Python. Test the beta releases! * If you have a bunch of Python scripts. Test the beta releases! * If you use Python for work, research, teaching or literally for anything. Test the beta releases! * If you ... In summary: no matter who you are of what you do. Test the beta releases! Is **very** important for us that we identify all possible things that may break your code **before** the final release is done and we can only do this if you help us by testing the beta releases and then report anything that doesn't work! ## This is a beta preview of Python 3.11 Python 3.11 is still in development. 3.11.0b5 is the last of five planned beta release previews. Beta release previews are intended to give the wider community the opportunity to test new features and bug fixes and to prepare their projects to support the new feature release. We **strongly encourage** maintainers of third-party Python projects to **test with 3.11** during the beta phase and report issues found to [the Python bug tracker](https://github.com/python/cpython/issues) as soon as possible. While the release is planned to be feature complete entering the beta phase, it is possible that features may be modified or, in rare cases, deleted up until the start of the release candidate phase (Monday, 2021-08-02). Our goal is have no ABI changes after beta 5 and as few code changes as possible after 3.11.0rc1, the first release candidate. To achieve that, it will be **extremely important** to get as much exposure for 3.11 as possible during the beta phase. Please keep in mind that this is a preview release and its use is **not** recommended for production environments. # Major new features of the 3.11 series, compared to 3.10 Some of the new major new features and changes in Python 3.11 are: ## General changes * [PEP 657](https://www.python.org/dev/peps/pep-0657/) -- Include Fine-Grained Error Locations in Tracebacks * [PEP 654](https://www.python.org/dev/peps/pep-0654/) -- Exception Groups and except* * [PEP 680](https://www.python.org/dev/peps/pep-0680/)-- tomllib: Support for Parsing TOML in the Standard Library * [PEP 681](https://www.python.org/dev/peps/pep-0681/)-- Data Class Transforms * [bpo-46752](https://github.com/python/cpython/issues/90908)-- Introduce task groups to asyncio * [bpo-433030](https://github.com/python/cpython/issues/34627/) -- Atomic grouping ((?>...)) and possessive quantifiers (`*+, ++, ?+, {m,n}+`) are now supported in regular expressions. * The [Faster Cpython Project](https://github.com/faster-cpython/) is already yielding some exciting results. Python 3.11 is up to 10-60% faster than Python 3.10. On average, we measured a 1.22x speedup on the standard benchmark suite. See [Faster CPython]( https://docs.python.org/3.11/whatsnew/3.11.html#faster-cpython) for details. ## Typing and typing language changes * [PEP 673](https://www.python.org/dev/peps/pep-0673/) -- Self Type * [PEP 646](https://www.python.org/dev/peps/pep-0646/)-- Variadic Generics * [PEP 675](https://www.python.org/dev/peps/pep-0675/)-- Arbitrary Literal String Type * [PEP 655](https://www.python.org/dev/peps/pep-0655/)-- Marking individual TypedDict items as required or potentially-missing <small>(Hey, **fellow core developer,** if a feature you find important is missing from this list, [let Pablo know](mailto:pablogsal@python.org ).)</small> The next pre-release of Python 3.11 will be 3.11.0rc1, currently scheduled for Monday, 2022-08-01. # More resources * [Online Documentation](https://docs.python.org/3.11/) * [PEP 664](https://www.python.org/dev/peps/pep-0664/), 3.11 Release Schedule * Report bugs at [ https://github.com/python/cpython/issues](https://github.com/python/cpython… . * [Help fund Python and its community](/psf/donations/). # And now for something completely different Schwarzschild wormholes, also known as Einstein–Rosen bridges (named after Albert Einstein and Nathan Rosen), are connections between areas of space that can be modelled as vacuum solutions to the Einstein field equations, and that are now understood to be intrinsic parts of the maximally extended version of the Schwarzschild metric describing an eternal black hole with no charge and no rotation. Here, "maximally extended" refers to the idea that spacetime should not have any "edges": it should be possible to continue this path arbitrarily far into the particle's future or past for any possible trajectory of a free-falling particle (following a geodesic in the spacetime). The Einstein–Rosen bridge was discovered by Ludwig Flamm in 1916, a few months after Schwarzschild published his solution, and was rediscovered by Albert Einstein and his colleague Nathan Rosen, who published their result in 1935. However, in 1962, John Archibald Wheeler and Robert W. Fuller published a paper showing that this type of wormhole is unstable if it connects two parts of the same universe and that it will pinch off too quickly for light (or any particle moving slower than light) that falls in from one exterior region to make it to the other exterior region. Although Schwarzschild wormholes are not traversable in both directions, their existence inspired Kip Thorne to imagine traversable wormholes created by holding the "throat" of a Schwarzschild wormhole open with exotic matter (material that has negative mass/energy). # Release hashes The BSD-style checksum hashes for the release artefacts are: SHA256 (python-3.11.0b5-amd64.exe) = 0cf9d582da862f2fe207fd54b81dfca110e8f04f4b05ab8c3228ce1ea060c7af SHA256 (python-3.11.0b5-arm64.exe) = a71efd9d3835d493d8207a30916ce3417af17295c02a9b0783dc740754f6e40b SHA256 (python-3.11.0b5-embed-amd64.zip) = 5584ddbd21f45ce74ce0512eeb1d817d15374b1b7a461d79f973f6dd48ab5d9e SHA256 (python-3.11.0b5-embed-arm64.zip) = 819924f10eb08ea6322b6040a2fb953137866bb1034cd4e8fe6e93c7c0b37e31 SHA256 (python-3.11.0b5-embed-win32.zip) = 18927604bcbe3c226be7864cde0c1f25ad35c6333d9d3125dfff8ca4fc872255 SHA256 (python-3.11.0b5.exe) = 382eb4c6dc1606bd3cf6f4bdeec8e1e7dab444c5aa23b86142d608a480d7c195 SHA256 (python-3.11.0b5-macos11.pkg) = cd8e6d98e79a4adcd376c486405a535b004cf9a58a71487a11bc424acd815012 SHA256 (Python-3.11.0b5.tar.xz) = 3810bd22f7dc34a99c2a2eb4b85264a4df4f05ef59c4e0ccc2ea82ee9c491698 SHA256 (Python-3.11.0b5.tgz) = 3f7d1a4ab0e64425f4ffd92d49de192ad2ee1c62bc52e3877e9f7b254c702e60 The hashes are also attached to this email. # 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/ If you have any questions, please reach out to me or another member of the release team :) Your friendly release team, Ned Deily @nad https://discuss.python.org/u/nad Steve Dower @steve.dower https://discuss.python.org/u/steve.dower Pablo Galindo Salgado @pablogsal https://discuss.python.org/u/pablogsal

1 0

New triagers: Thomas Grainger and Michael Droettboom
by Christian Heimes 23 Jul '22

23 Jul '22

Please welcome our newest triagers: Thomas Grainger, who is the maintainer of anyio and has been fixing asyncio bugs in the past three years. https://github.com/python/core-workflow/issues/471 Michael Droettboom, who is the creator of Pyodide (Python in the browser) and has helped to unblock 3.11b release. https://github.com/python/core-workflow/issues/472 Regards, Christian

1 0

[RELEASE] The cursed fourth Python 3.11 beta (3.11.0b4) is available
by Pablo Galindo Salgado 11 Jul '22

11 Jul '22

I cannot believe I am writing this, but Python 3.11.b4 is finally available!! [image: :scream:] [image: :tada:] [image: :tada:] [image: :tada:] https://www.python.org/downloads/release/python-3110b4/ ##[image: :warning:][image: :warning:][image: :warning:] PLEASE HELP US TO TEST THIS RELEASE [image: :warning:][image: :warning:][image: :warning:] Due to the modified release schedule and the stability concerns regarding the past beta releases, please, please, please, please, help us to test Python 3.11 by testing this beta releases. * if you maintain a library or a third-party package. Test the beta releases! * If you have code that you maintain at work/research centre/classroom/whatever. Test the beta releases! * If you are a multi-million corporation that uses Python. Test the beta releases! * If you are a single-person company that uses Python. Test the beta releases! * If you have a bunch of Python scripts. Test the beta releases! * If you use Python for work, research, teaching or literally for anything. Test the beta releases! * If you ... In summary: no matter who you are or what you do. Test the beta releases! Is **very** important for us that we identify all possible things that may break your code **before** the final release is done and we can only do this if you help us by testing the beta releases and then report anything that doesn't work! ## Credit where credit is due [image: :pray:] Lots of thanks to Christian Heimes, Brandt Bucher, Irit Katriel, Mark Shannon, Dennis Sweeney, Kumar Aditya and other contributors (sorry if I am missing any names) that worked really hard against time to help me and the release team with the release blockers. They are all awesome and we and the Python community are very lucky to have them in the team [image: :heart:] ## What happens with the next betas? As stated in [my previous communication]( https://mail.python.org/archives/list/python-dev@python.org/thread/3JWVCSBP…) we are in a special situation regarding beta releases. As the requirements to continue with the regular schedule are met, we are going to still target the final release of Monday, 2022-10-03. Python 3.11.0b5 was supposed to be released two days ago, so we are obviously delayed. As we are targeting the regular release schedule, I'm going to try to release 3.11.0b5 on Thursday, 2022-07-25. ## This is a beta preview of Python 3.11 Python 3.11 is still in development. 3.11.0b4 is the fourth of five planned beta release previews. Beta release previews are intended to give the wider community the opportunity to test new features and bug fixes and to prepare their projects to support the new feature release. We **strongly encourage** maintainers of third-party Python projects to **test with 3.11** during the beta phase and report issues found to [the Python bug tracker](https://github.com/python/cpython/issues) as soon as possible. While the release is planned to be feature complete entering the beta phase, it is possible that features may be modified or, in rare cases, deleted up until the start of the release candidate phase (Monday, 2021-08-02). Our goal is have no ABI changes after beta 5 and as few code changes as possible after 3.11.0rc1, the first release candidate. To achieve that, it will be **extremely important** to get as much exposure for 3.11 as possible during the beta phase. Please keep in mind that this is a preview release and its use is **not** recommended for production environments. # Major new features of the 3.11 series, compared to 3.10 Some of the new major new features and changes in Python 3.11 are: ## General changes * [PEP 657](https://www.python.org/dev/peps/pep-0657/) -- Include Fine-Grained Error Locations in Tracebacks * [PEP 654](https://www.python.org/dev/peps/pep-0654/) -- Exception Groups and except* * [PEP 680](https://www.python.org/dev/peps/pep-0680/)-- tomllib: Support for Parsing TOML in the Standard Library * [PEP 681](https://www.python.org/dev/peps/pep-0681/)-- Data Class Transforms * [bpo-46752](https://bugs.python.org/issue46752)-- Introduce task groups to asyncio * [bpo-433030](https://github.com/python/cpython/issues/34627/) -- Atomic grouping ((?>...)) and possessive quantifiers (`*+, ++, ?+, {m,n}+`) are now supported in regular expressions. * The [Faster Cpython Project](https://github.com/faster-cpython/) is already yielding some exciting results. Python 3.11 is up to 10-60% faster than Python 3.10. On average, we measured a 1.22x speedup on the standard benchmark suite. See [Faster CPython]( https://docs.python.org/3.11/whatsnew/3.11.html#faster-cpython) for details. ## Typing and typing language changes * [PEP 673](https://www.python.org/dev/peps/pep-0673/) -- Self Type * [PEP 646](https://www.python.org/dev/peps/pep-0646/)-- Variadic Generics * [PEP 675](https://www.python.org/dev/peps/pep-0675/)-- Arbitrary Literal String Type * [PEP 655](https://www.python.org/dev/peps/pep-0655/)-- Marking individual TypedDict items as required or potentially-missing <small>(Hey, **fellow core developer,** if a feature you find important is missing from this list, [let Pablo know](mailto:pablogsal@python.org ).)</small> The next pre-release of Python 3.11 will be 3.11.0b5, currently scheduled for Thursday, 2022-07-25. # More resources * [Online Documentation](https://docs.python.org/3.11/) * [PEP 664](https://www.python.org/dev/peps/pep-0664/), 3.11 Release Schedule * Report bugs at [https://bugs.python.org](https://bugs.python.org). * [Help fund Python and its community](/psf/donations/). # And now for something completely different The Planck temperature is 1.416784×10**32 K. At this temperature, the wavelength of light emitted by thermal radiation reaches the Planck length. There are no known physical models able to describe temperatures greater than the Planck temperature and a quantum theory of gravity would be required to model the extreme energies attained. Hypothetically, a system in thermal equilibrium at the Planck temperature might contain Planck-scale black holes, constantly being formed from thermal radiation and decaying via Hawking evaporation; adding energy to such a system might decrease its temperature by creating larger black holes, whose Hawking temperature is lower. Rumours say the Planck temperature can be reached in some of the hottest parts of Spain in summer. # 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/ If you have any questions, please reach out to me or another member of the release team :) Your friendly release team, Ned Deily @nad https://discuss.python.org/u/nad Steve Dower @steve.dower https://discuss.python.org/u/steve.dower Pablo Galindo Salgado @pablogsal https://discuss.python.org/u/pablogsal

1 1

Starting the release of Python 3.11.0b4
by Pablo Galindo Salgado 11 Jul '22

11 Jul '22

Hi everyone, As a heads up: I'm starting the release of Python 3.11.0b4 and to avoid complicating things I have blocked the 3.11 branch until the release finishes so don't worry if you are not able to merge stuff in the 3.11 branch: nobody as removed your committer powers :) Cheers from sunny London, Pablo Galindo Salgado

1 0

[Release] Status of Python 3.11 release
by Pablo Galindo Salgado 04 Jul '22

04 Jul '22

Hi everyone, # TLDR We may be pushing the final release until December if the stability of Python 3.11 doesn't improve. # Long Explanation Unfortunately, we cannot still release the next Python 3.11 beta release (3.11.0b4) because we still have a bunch of pending release blockers. Unfortunately, this is still after several preexisting release blockers have been fixed, some of them being discovered after I sent my last update. These are the current release blockers: https://github.com/python/cpython/issues?q=is%3Aissue+is%3Aopen+sort%3Aupda… We also have some deferred blockers (some of them should actually be release blockers): https://github.com/python/cpython/issues?q=is%3Aissue+is%3Aopen+sort%3Aupda… Due to this and the fact that we are already 3 weeks delayed in the release schedule, the current stability of Python 3.11 is not as good as it is supposed to be at this stage of the release schedule and more testing from end-users and library authors is required. After discussing with the Steering Council, we are considering delaying the final release until December to allow for two more beta releases. This is how we are going to proceed: * If the current release blockers are not fixed by the end of this week, two more betas will be released (1 month per beta) and we will *definitely* delay the final release until December. * If the current release blockers are fixed we will proceed to release Python 3.11.0b4 on Monday. We will target the current release date (Monday, 2022-10-03) but if more release blockers that affect fundamental parts of the Python interpreter or the standard libraries are raised, the release team will still consider adding two more betas nd pushing the final release to December. One of the goals that we are going to try to achieve from the release team is that no substantial code changes are added between the last beta and the first release candidate. This is so all the fixes that affect fundamental parts of the interpreter or the standard library can be tested by end-users before the first release candidate is released (and not with it). This is also partially because once we release the first release candidate, the ABI will be frozen and certain kinds of fixes will be more complicated. Hopefully, this addresses some of you that have reached out with concerns over the stability of Python 3.11 and the release schedule. I understand that delaying the release until December will complicate things for some Linux distributions and will affect end users and redistributors targeting the original release, but please understand that our responsibility in the release team after all is to guarantee a stable final release above all and unfortunately, we don't currently have the confidence that we would like given the current state of the release process. Please do not hesitate in reaching out if you have any questions or concerns. Thanks, everyone for your help and understanding and thanks a lot to all of you for your great work! Cheers from cloudy London, Pablo Galindo Salgado

1 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

python-committers July 2022