Mailman 3 March 2021 - python-committers

Re: [Python-Dev] Re: [Release management] schedule for renaming the default branch
by Pablo Galindo Salgado 10 Mar '21

10 Mar '21

I am answering this as a member of the release management team, not as an official response from the SC. > and understand who the identified impacted parties are All developers that have clones of the repository and any party maintaining any script that interacts with the default CPython branch. > and what the plan is to notify them These messages on python-dev and python-comitters + messages in the official release announcement and notes. > and help them update within this timescale For the repositories, execute the commands listed in the previous message. For scrips and other references to the main branch, they need to do the change themselves but in most cases is a simple rename master->main. > Has this analysis been published anywhere No. It has been discussed by the Steering Council as you can see in the February update: https://github.com/python/steering-council/blob/main/updates/2021-02-steeri… On Wed, 10 Mar 2021 at 14:21, Stestagg <stestagg(a)gmail.com> wrote: > Hi > > I would be great to read the impact analysis for this change, and > understand who the identified impacted parties are, and what the plan is to > notify them and help them update within this timescale. > > Has this analysis been published anywhere? I know there are lots of places > where discussions/documentation happens > > Thanks > > Steve > > > > On Wed, Mar 10, 2021 at 2:10 PM Pablo Galindo Salgado <pablogsal(a)gmail.com> > wrote: > >> Hi, >> >> I am writing on behalf of the Python Release Management team. The >> Steering Council has requested the RM team to schedule >> and perform the necessary changes to rename the default branch from >> master to main. >> >> # The changes >> >> What follows is the technical description of the changes and the >> timeline. In order to keep this thread focused on this particular >> aspect, if you wish to discuss anything related to the change itself, >> please, open a new email thread or reuse an existing one. >> >> - The change will be executed ***when beta 1 is released***, as the >> beta 1 release requires some branching engineering already >> to create the 3.10 branch and point 3.11 to the new one as well as >> changing CI, buildbots...etc ** >> *This is scheduled for Monday, 2021-05-03**.* >> - The CI will be adapted to work with the new "main" branch. >> - The buildbots will be adapted to work with the new "main" branch. >> - Branch protection rules will be adapted. >> - The different bots will be adapted by the respective bot maintainer >> teams. >> - All the URLs that point to master in the README and other places >> will be adapted to point to main instead (notice this is >> not strictly necessary because GitHub redirects automatically). >> >> Notice that the renaming will automatically: >> >> >> - Re-target any open pull requests >> - Update any draft releases based on the branch >> - Move any branch protection rules that explicitly reference the old >> name >> - Show a notice to repository contributors, maintainers, and admins >> on the repository homepage with instructions to update local copies of the >> repository >> - Show a notice to contributors who git push to the old branch >> - Redirect web requests for the old branch name to the new branch name >> - Return a "Moved Permanently" response in API requests for the old >> branch name >> >> Check this <https://github.com/github/renaming> for more information. >> >> # What you need to do? >> >> You just need to update your local clone after the branch name changes. >> From the local clone of the repository on a computer, >> run the following commands to update the name of the default branch. >> >> $ git branch -m master main >> $ git fetch origin >> $ git branch -u origin/main main >> >> Apart from that, you should update any local script or command that uses >> the name "master" to use the name "main". >> >> Regards from windy London, >> Pablo Galindo Salgado >> _______________________________________________ >> Python-Dev mailing list -- python-dev(a)python.org >> To unsubscribe send an email to python-dev-leave(a)python.org >> https://mail.python.org/mailman3/lists/python-dev.python.org/ >> Message archived at >> https://mail.python.org/archives/list/python-dev@python.org/message/QWW7KGB… >> Code of Conduct: http://python.org/psf/codeofconduct/ >> > _______________________________________________ > Python-Dev mailing list -- python-dev(a)python.org > To unsubscribe send an email to python-dev-leave(a)python.org > https://mail.python.org/mailman3/lists/python-dev.python.org/ > Message archived at > https://mail.python.org/archives/list/python-dev@python.org/message/66RS2S6… > Code of Conduct: http://python.org/psf/codeofconduct/ >

1 0

[Release management] schedule for renaming the default branch
by Pablo Galindo Salgado 10 Mar '21

10 Mar '21

Hi, I am writing on behalf of the Python Release Management team. The Steering Council has requested the RM team to schedule and perform the necessary changes to rename the default branch from master to main. # The changes What follows is the technical description of the changes and the timeline. In order to keep this thread focused on this particular aspect, if you wish to discuss anything related to the change itself, please, open a new email thread or reuse an existing one. - The change will be executed ***when beta 1 is released***, as the beta 1 release requires some branching engineering already to create the 3.10 branch and point 3.11 to the new one as well as changing CI, buildbots...etc ** *This is scheduled for Monday, 2021-05-03**.* - The CI will be adapted to work with the new "main" branch. - The buildbots will be adapted to work with the new "main" branch. - Branch protection rules will be adapted. - The different bots will be adapted by the respective bot maintainer teams. - All the URLs that point to master in the README and other places will be adapted to point to main instead (notice this is not strictly necessary because GitHub redirects automatically). Notice that the renaming will automatically: - Re-target any open pull requests - Update any draft releases based on the branch - Move any branch protection rules that explicitly reference the old name - Show a notice to repository contributors, maintainers, and admins on the repository homepage with instructions to update local copies of the repository - Show a notice to contributors who git push to the old branch - Redirect web requests for the old branch name to the new branch name - Return a "Moved Permanently" response in API requests for the old branch name Check this <https://github.com/github/renaming> for more information. # What you need to do? You just need to update your local clone after the branch name changes. From the local clone of the repository on a computer, run the following commands to update the name of the default branch. $ git branch -m master main $ git fetch origin $ git branch -u origin/main main Apart from that, you should update any local script or command that uses the name "master" to use the name "main". Regards from windy London, Pablo Galindo Salgado

1 0

Is Tests / Ubuntu broken at the moment?
by Senthil Kumaran 03 Mar '21

03 Mar '21

Hello Python Developers, I notice TLS tests failing in the ssl test suite in master, 3.9 and 3.8 branches. https://github.com/python/cpython/runs/2018191733 Is it to do with infrastructure, certificate? I am unable to determine it exactly. The failure is observed upon merge to master. or with 3.8, 3.9 backports of any PR. Thank you, Senthil

5 9

Python 3.10.0a6 is available, now with 100% more pattern matching
by Pablo Galindo Salgado 02 Mar '21

02 Mar '21

Remember us? It's your friendly CPython release team and we have something we think you may like: The new alpha release of Python 3.10 is here, now with 100% more pattern matching. If I were you, I would download it and start playing with it. Extra points if you report us any bugs you find along the way! Are you confused about all this pattern matching business? Fear not, this release also includes some fantastic documentation and some shiny new "What's new" entries. Check them here and tell us how we can improve it: What's new: https://docs.python.org/3.10/whatsnew/3.10.html Tutorial: https://docs.python.org/3.10/tutorial/controlflow.html#match-statements Go get the new alpha here: https://www.python.org/downloads/release/python-3100a6/ **This is an early developer preview of Python 3.10** # Major new features of the 3.10 series, compared to 3.9 Python 3.10 is still in development. This release, 3.10.0a6 is the sixth of seven planned alpha releases. Alpha releases are intended to make it easier to test the current state of new features and bug fixes and to test the release process. During the alpha phase, features may be added up until the start of the beta phase (2021-05-03) and, if necessary, may be modified or deleted up until the release candidate phase (2021-10-04). Please keep in mind that this is a preview release and its use is **not** recommended for production environments. Many new features for Python 3.10 are still being planned and written. Among the new major new features and changes so far: * [PEP 623](https://www.python.org/dev/peps/pep-0623/) -- Remove wstr from Unicode * [PEP 604](https://www.python.org/dev/peps/pep-0604/) -- Allow writing union types as X | Y * [PEP 612](https://www.python.org/dev/peps/pep-0612/) -- Parameter Specification Variables * [PEP 626](https://www.python.org/dev/peps/pep-0626/) -- Precise line numbers for debugging and other tools. * [bpo-38605](https://bugs.python.org/issue38605): `from __future__ import annotations` ([PEP 563](https://www.python.org/dev/peps/pep-0563/)) is now the default. * [PEP 618 ](https://www.python.org/dev/peps/pep-0618/) -- Add Optional Length-Checking To zip. * [bpo-12782](https://bugs.python.org/issue12782): Parenthesized context managers are now officially allowed. * [PEP 632 ](https://www.python.org/dev/peps/pep-0632/) -- Deprecate distutils module. * [PEP 613 ](https://www.python.org/dev/peps/pep-0613/) -- Explicit Type Aliases * [PEP 634 ](https://www.python.org/dev/peps/pep-0634/) -- Structural Pattern Matching: Specification * [PEP 635 ](https://www.python.org/dev/peps/pep-0635/) -- Structural Pattern Matching: Motivation and Rationale * [PEP 636 ](https://www.python.org/dev/peps/pep-0636/) -- Structural Pattern Matching: Tutorial * <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.10 will be 3.10.0a7 ( last alpha release), currently scheduled for Monday, 2021-04-05. # More resources * [Online Documentation](https://docs.python.org/3.10/) * [PEP 619](https://www.python.org/dev/peps/pep-0619/), 3.10 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 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 the 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). 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). Regards from rainy London, Pablo Galindo Salgado

1 0

[RELEASE] Python 3.10.0a6 is available, now with 100% more pattern matching
by Pablo Galindo Salgado 02 Mar '21

02 Mar '21

Remember us? It's your friendly CPython release team and we have something we think you may like: The new alpha release of Python 3.10 is here, now with 100% more pattern matching. If I were you, I would download it and start playing with it. Extra points if you report us any bugs you find along the way! Are you confused about all this pattern matching business? Fear not, this release also includes some fantastic documentation and some shiny new "What's new" entries. Check them here and tell us how we can improve it: What's new: https://docs.python.org/3.10/whatsnew/3.10.html Tutorial: https://docs.python.org/3.10/tutorial/controlflow.html#match-statements Go get the new alpha here: https://www.python.org/downloads/release/python-3100a6/ *Note: The alpha was officially released yesterday, but my email client failed to deliver this email to the mailing lists so I am reposting it.* **This is an early developer preview of Python 3.10** # Major new features of the 3.10 series, compared to 3.9 Python 3.10 is still in development. This release, 3.10.0a6 is the sixth of seven planned alpha releases. Alpha releases are intended to make it easier to test the current state of new features and bug fixes and to test the release process. During the alpha phase, features may be added up until the start of the beta phase (2021-05-03) and, if necessary, may be modified or deleted up until the release candidate phase (2021-10-04). Please keep in mind that this is a preview release and its use is **not** recommended for production environments. Many new features for Python 3.10 are still being planned and written. Among the new major new features and changes so far: * [PEP 623](https://www.python.org/dev/peps/pep-0623/) -- Remove wstr from Unicode * [PEP 604](https://www.python.org/dev/peps/pep-0604/) -- Allow writing union types as X | Y * [PEP 612](https://www.python.org/dev/peps/pep-0612/) -- Parameter Specification Variables * [PEP 626](https://www.python.org/dev/peps/pep-0626/) -- Precise line numbers for debugging and other tools. * [bpo-38605](https://bugs.python.org/issue38605): `from __future__ import annotations` ([PEP 563](https://www.python.org/dev/peps/pep-0563/)) is now the default. * [PEP 618 ](https://www.python.org/dev/peps/pep-0618/) -- Add Optional Length-Checking To zip. * [bpo-12782](https://bugs.python.org/issue12782): Parenthesized context managers are now officially allowed. * [PEP 632 ](https://www.python.org/dev/peps/pep-0632/) -- Deprecate distutils module. * [PEP 613 ](https://www.python.org/dev/peps/pep-0613/) -- Explicit Type Aliases * [PEP 634 ](https://www.python.org/dev/peps/pep-0634/) -- Structural Pattern Matching: Specification * [PEP 635 ](https://www.python.org/dev/peps/pep-0635/) -- Structural Pattern Matching: Motivation and Rationale * [PEP 636 ](https://www.python.org/dev/peps/pep-0636/) -- Structural Pattern Matching: Tutorial * <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.10 will be 3.10.0a7 ( last alpha release), currently scheduled for Monday, 2021-04-05. # More resources * [Online Documentation](https://docs.python.org/3.10/) * [PEP 619](https://www.python.org/dev/peps/pep-0619/), 3.10 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 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 the 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). 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). Regards from rainy London, Pablo Galindo Salgado

1 0