[Python-Dev] Re: Please welcome our next Release Manager, Pablo!

[Victor Stinner]

Le mer. 20 mai 2020 à 02:39, Terry Reedy  a écrit :
> First, with 2.x really past us, is removing remaining long deprecated
> features, plus some others advocated for removal.  I think these are
> best done by the first alpha so that early testers are rewarded with an
> early opportunity to change their code or else object to the removal.

I tried to remove as much deprecated features as possible at the
beginning of the 3.9 dev cycle. Many people contributed to this task,
see the length of the Removal section :-)
https://docs.python.org/dev/whatsnew/3.9.html#removed

Later, aliases to ABC in the collections and the "U" mode of open()
were reverted in 3.9, with the idea of removing them again in 3.10.
Just to give one cycle to the community to drop Python 2 and fix these
deprecation warnings. The What's New In Python 3.9 documentation
starts with a long warning about deprecation warnings:
https://docs.python.org/dev/whatsnew/3.9.html#you-should-check-for-deprecationwarning-in-your-code

Victor
-- 
Night gathers, and now my watch begins. It shall not end until my death.
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@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/UFCOMRV4EBWQ4PAQPN5FETFQLWEJFMQS/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: [python-committers] Please welcome our next Release Manager, Pablo!

[Senthil Kumaran]

Congratulations, Pablo!

Thank you for taking care of buildbots, and donning this new role.


On Tue, May 19, 2020 at 3:54 PM Barry Warsaw  wrote:

> In light of the release of Python 3.9b1, let’s take a moment to celebrate
> all the great work that our Python 3.8 and 3.9 release manager Łukasz has
> done.  The role of Python Release Manager is hugely important to each
> successful release, and it can be a lot of work, often unseen and thankless
> to shepherd a new Python version through its first alpha release to its
> last security release.  With all of your immeasurable help, the Release
> Manager ensures solid, feature-full releases that the entire Python
> community eagerly awaits.
>
> Łukasz carries on the fine tradition of all of our past release managers,
> and now that his second release has entered beta phase, I’m very happy to
> announce our next Release Manager, for Python 3.10 and 3.11: Pablo Galindo
> Salgado!
>
> Since becoming a core developer in 2018, Pablo has contributed
> significantly to Python.  With the change to an annual release cycle (PEP
> 602, authored by Łukasz), the time commitment for release managers has been
> reduced as well, and we will continue to look for ways to make the
> selection process for release managers more transparent and accessible.  I
> know that in addition to admirably managing the releases for 3.10 and 3.11,
> Pablo will also help to continually improve the process of selecting and
> serving as release manager.
>
> Please join me in welcoming Pablo in his new role!
>
> Cheers,
> -Barry
>
> ___
> python-committers mailing list -- python-committ...@python.org
> To unsubscribe send an email to python-committers-le...@python.org
> https://mail.python.org/mailman3/lists/python-committers.python.org/
> Message archived at
> https://mail.python.org/archives/list/python-committ...@python.org/message/44TLJO5YX6XYM4ICWSHMBMCKPBBQQP5S/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@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/6I2IJ332M7NKAFV5O7C46NVWR2M2226M/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: Please welcome our next Release Manager, Pablo!

[Terry Reedy]

On 5/19/2020 6:54 PM, Barry Warsaw wrote:

I’m very happy to announce our next Release Manager, for Python 3.10 and 3.11: 
Pablo Galindo Salgado!


I think having a buildbot watcher as release manager will be great.  I 
see 2 major, possible contentious issues for the next two releases.


First, with 2.x really past us, is removing remaining long deprecated 
features, plus some others advocated for removal.  I think these are 
best done by the first alpha so that early testers are rewarded with an 
early opportunity to change their code or else object to the removal.


Second is removal of the old parser and grammar changes the require the 
new parser.



--
Terry Jan Reedy

___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@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/D2F6OOTTRUX33I2NOMU6M4TGVXUE6ZF5/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: [python-committers] Please welcome our next Release Manager, Pablo!

[joannah nanjekye]

 Thanks for the good work Łukasz!

And congrats to the well deserved Pablo.

On Tue, May 19, 2020 at 7:54 PM Barry Warsaw  wrote:

> In light of the release of Python 3.9b1, let’s take a moment to celebrate
> all the great work that our Python 3.8 and 3.9 release manager Łukasz has
> done.  The role of Python Release Manager is hugely important to each
> successful release, and it can be a lot of work, often unseen and thankless
> to shepherd a new Python version through its first alpha release to its
> last security release.  With all of your immeasurable help, the Release
> Manager ensures solid, feature-full releases that the entire Python
> community eagerly awaits.
>
> Łukasz carries on the fine tradition of all of our past release managers,
> and now that his second release has entered beta phase, I’m very happy to
> announce our next Release Manager, for Python 3.10 and 3.11: Pablo Galindo
> Salgado!
>
> Since becoming a core developer in 2018, Pablo has contributed
> significantly to Python.  With the change to an annual release cycle (PEP
> 602, authored by Łukasz), the time commitment for release managers has been
> reduced as well, and we will continue to look for ways to make the
> selection process for release managers more transparent and accessible.  I
> know that in addition to admirably managing the releases for 3.10 and 3.11,
> Pablo will also help to continually improve the process of selecting and
> serving as release manager.
>
> Please join me in welcoming Pablo in his new role!
>
> Cheers,
> -Barry
>
> ___
> python-committers mailing list -- python-committ...@python.org
> To unsubscribe send an email to python-committers-le...@python.org
> https://mail.python.org/mailman3/lists/python-committers.python.org/
> Message archived at
> https://mail.python.org/archives/list/python-committ...@python.org/message/44TLJO5YX6XYM4ICWSHMBMCKPBBQQP5S/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>


-- 
Best,
Joannah Nanjekye

*"You think you know when you learn, are more sure when you can write, even
more when you can teach, but certain when you can program." Alan J. Perlis*
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@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/ZITJ23PNXXBEGQXXFAFVWQFZWUHGC54E/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: [python-committers] Please welcome our next Release Manager, Pablo!

[Łukasz Langa]

I'm very happy about this!

Pablo is a natural candidate for the role. As one of the people caring for our 
buildbots, he helped me during releases many times. And this past 3.9.0b1, 
while I was working on the new 3.9 maintenance branch, he made the master 
branch successfully build a Python with a double-digit minor version number. 
Strong start!

Welcome!

PS. Thank you for the kind words, Barry, it will take some more releases for me 
to make before I retire: eyes fixed on 3.9.0 in particular. Exciting times! :-)

-- 
Best regards,
Łukasz Langa

> On 20 May 2020, at 00:54, Barry Warsaw  wrote:
> 
> In light of the release of Python 3.9b1, let’s take a moment to celebrate 
> all the great work that our Python 3.8 and 3.9 release manager Łukasz has 
> done.  The role of Python Release Manager is hugely important to each 
> successful release, and it can be a lot of work, often unseen and thankless 
> to shepherd a new Python version through its first alpha release to its last 
> security release.  With all of your immeasurable help, the Release Manager 
> ensures solid, feature-full releases that the entire Python community eagerly 
> awaits.
> 
> Łukasz carries on the fine tradition of all of our past release managers, and 
> now that his second release has entered beta phase, I’m very happy to 
> announce our next Release Manager, for Python 3.10 and 3.11: Pablo Galindo 
> Salgado!
> 
> Since becoming a core developer in 2018, Pablo has contributed significantly 
> to Python.  With the change to an annual release cycle (PEP 602, authored by 
> Łukasz), the time commitment for release managers has been reduced as well, 
> and we will continue to look for ways to make the selection process for 
> release managers more transparent and accessible.  I know that in addition to 
> admirably managing the releases for 3.10 and 3.11, Pablo will also help to 
> continually improve the process of selecting and serving as release manager.
> 
> Please join me in welcoming Pablo in his new role!
> 
> Cheers,
> -Barry
> 
> ___
> python-committers mailing list -- python-committ...@python.org
> To unsubscribe send an email to python-committers-le...@python.org
> https://mail.python.org/mailman3/lists/python-committers.python.org/
> Message archived at 
> https://mail.python.org/archives/list/python-committ...@python.org/message/44TLJO5YX6XYM4ICWSHMBMCKPBBQQP5S/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@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/EBUGAIJWJ6DVL2IYHBJQSQGVIK2TV6SD/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: [python-committers] Please welcome our next Release Manager, Pablo!

[Kyle Stanley]

> In light of the release of Python 3.9b1, let’s take a moment to celebrate
all the great work that our Python 3.8 and 3.9 release manager Łukasz has
done.

Thank you so much to Łukasz for a fantastic 3.8 release, and for the smooth
transition into 3.9 beta. :-)

> Please join me in welcoming Pablo in his new role!

Congrats, Pablo! With all of your incredible work on CPython's continuous
integration, I think you'll be a great release manager!

On Tue, May 19, 2020 at 6:54 PM Barry Warsaw  wrote:

> In light of the release of Python 3.9b1, let’s take a moment to celebrate
> all the great work that our Python 3.8 and 3.9 release manager Łukasz has
> done.  The role of Python Release Manager is hugely important to each
> successful release, and it can be a lot of work, often unseen and thankless
> to shepherd a new Python version through its first alpha release to its
> last security release.  With all of your immeasurable help, the Release
> Manager ensures solid, feature-full releases that the entire Python
> community eagerly awaits.
>
> Łukasz carries on the fine tradition of all of our past release managers,
> and now that his second release has entered beta phase, I’m very happy to
> announce our next Release Manager, for Python 3.10 and 3.11: Pablo Galindo
> Salgado!
>
> Since becoming a core developer in 2018, Pablo has contributed
> significantly to Python.  With the change to an annual release cycle (PEP
> 602, authored by Łukasz), the time commitment for release managers has been
> reduced as well, and we will continue to look for ways to make the
> selection process for release managers more transparent and accessible.  I
> know that in addition to admirably managing the releases for 3.10 and 3.11,
> Pablo will also help to continually improve the process of selecting and
> serving as release manager.
>
> Please join me in welcoming Pablo in his new role!
>
> Cheers,
> -Barry
>
> ___
> python-committers mailing list -- python-committ...@python.org
> To unsubscribe send an email to python-committers-le...@python.org
> https://mail.python.org/mailman3/lists/python-committers.python.org/
> Message archived at
> https://mail.python.org/archives/list/python-committ...@python.org/message/44TLJO5YX6XYM4ICWSHMBMCKPBBQQP5S/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@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/J3CGQNJ2UH3RPFJ2IEVGERTIRAMGXOLI/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: [python-committers] Please welcome our next Release Manager, Pablo!

[Guido van Rossum]

Huge congrats, Pablo. And thanks to Lukasz for 3.8 and 3.9. They’re all the
greatest release ever!

On Tue, May 19, 2020 at 15:54 Barry Warsaw  wrote:

> In light of the release of Python 3.9b1, let’s take a moment to celebrate
> all the great work that our Python 3.8 and 3.9 release manager Łukasz has
> done.  The role of Python Release Manager is hugely important to each
> successful release, and it can be a lot of work, often unseen and thankless
> to shepherd a new Python version through its first alpha release to its
> last security release.  With all of your immeasurable help, the Release
> Manager ensures solid, feature-full releases that the entire Python
> community eagerly awaits.
>
> Łukasz carries on the fine tradition of all of our past release managers,
> and now that his second release has entered beta phase, I’m very happy to
> announce our next Release Manager, for Python 3.10 and 3.11: Pablo Galindo
> Salgado!
>
> Since becoming a core developer in 2018, Pablo has contributed
> significantly to Python.  With the change to an annual release cycle (PEP
> 602, authored by Łukasz), the time commitment for release managers has been
> reduced as well, and we will continue to look for ways to make the
> selection process for release managers more transparent and accessible.  I
> know that in addition to admirably managing the releases for 3.10 and 3.11,
> Pablo will also help to continually improve the process of selecting and
> serving as release manager.
>
> Please join me in welcoming Pablo in his new role!
>
> Cheers,
> -Barry
>
> ___
> python-committers mailing list -- python-committ...@python.org
> To unsubscribe send an email to python-committers-le...@python.org
> https://mail.python.org/mailman3/lists/python-committers.python.org/
> Message archived at
> https://mail.python.org/archives/list/python-committ...@python.org/message/44TLJO5YX6XYM4ICWSHMBMCKPBBQQP5S/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
-- 
--Guido (mobile)
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@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/AADUVN5OJTL365WQJGIHHN67DJJFR5XE/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Please welcome our next Release Manager, Pablo!

[Barry Warsaw]

In light of the release of Python 3.9b1, let’s take a moment to celebrate all 
the great work that our Python 3.8 and 3.9 release manager Łukasz has done.  
The role of Python Release Manager is hugely important to each successful 
release, and it can be a lot of work, often unseen and thankless to shepherd a 
new Python version through its first alpha release to its last security 
release.  With all of your immeasurable help, the Release Manager ensures 
solid, feature-full releases that the entire Python community eagerly awaits.

Łukasz carries on the fine tradition of all of our past release managers, and 
now that his second release has entered beta phase, I’m very happy to announce 
our next Release Manager, for Python 3.10 and 3.11: Pablo Galindo Salgado!

Since becoming a core developer in 2018, Pablo has contributed significantly to 
Python.  With the change to an annual release cycle (PEP 602, authored by 
Łukasz), the time commitment for release managers has been reduced as well, and 
we will continue to look for ways to make the selection process for release 
managers more transparent and accessible.  I know that in addition to admirably 
managing the releases for 3.10 and 3.11, Pablo will also help to continually 
improve the process of selecting and serving as release manager.

Please join me in welcoming Pablo in his new role!

Cheers,
-Barry



signature.asc
Description: Message signed with OpenPGP
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@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/44TLJO5YX6XYM4ICWSHMBMCKPBBQQP5S/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: PEP 584 underspecified

[David Mertz]

I comment on the PR.

On Tue, May 19, 2020 at 4:44 PM Brandt Bucher 
wrote:

> Maybe I'm missing something here. The PEP specifically says:
>
> > Similarly, the iteration order of the key-value pairs in the dictionary
> will follow the same semantics as the examples above, with each newly added
> key (and its value) being appended to the current sequence.
>
> That seems sufficient, no?
> ___
> Python-Dev mailing list -- python-dev@python.org
> To unsubscribe send an email to python-dev-le...@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/NM75M5N7BJOHSG3ZELIVBUNOG7ZQ3VQ4/
> Code of Conduct: http://python.org/psf/codeofconduct/
>


-- 
The dead increasingly dominate and strangle both the living and the
not-yet born.  Vampiric capital and undead corporate persons abuse
the lives and control the thoughts of homo faber. Ideas, once born,
become abortifacients against new conceptions.
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@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/S6EXHHRCO64F6CLEODZWLKTL4NJUVQJW/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: PEP 584 underspecified

[Brandt Bucher]

Maybe I'm missing something here. The PEP specifically says:

> Similarly, the iteration order of the key-value pairs in the dictionary will 
> follow the same semantics as the examples above, with each newly added key 
> (and its value) being appended to the current sequence.

That seems sufficient, no?
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@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/NM75M5N7BJOHSG3ZELIVBUNOG7ZQ3VQ4/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] Re: PEP 584 underspecified

[Guido van Rossum]

Yes, the assumption (and the implementation) is that newly added keys are
inserted at the end, in the order in which the second object produces them
when iterated over. Please do send us a PR for the peps repo!

On Tue, May 19, 2020 at 12:34 PM David Mertz  wrote:

> I know this is late in the cycle to think of this.  But I just realized
> the PEP 584 does not say anything about order guarantees.
>
> I think it is safe to assume that existing keys in dictA will not have
> order modified by `dictA |= dictB`.  However, the PEP does not state what
> order we are given when new keys are added.  I reckon it is a kind of
> insertion, so they must occur after the existing keys.  However, stating
> explicitly that the MUST  (or alternately MIGHT NOT) be inserted in the
> order that dictB has seems worth specifying.
>
> Moreover, the new operator explicitly states that it will flexibly deal
> with mapping types other than dict on the right hand side.  So what happens
> with:
>
> dictA |= unorderedmapB
>
> I think the "reasonable" belief should be that all new keys will be in
> some unspecified order amongst themselves, but all occurring after the old
> keys.  I think a sentence or two explicitly indicating what is promised and
> what is not would be worthwhile.
>
>>
>>-
>>
>>PEP 584 , Union Operators
>>in dict
>>
>> --
> The dead increasingly dominate and strangle both the living and the
> not-yet born.  Vampiric capital and undead corporate persons abuse
> the lives and control the thoughts of homo faber. Ideas, once born,
> become abortifacients against new conceptions.
> ___
> Python-Dev mailing list -- python-dev@python.org
> To unsubscribe send an email to python-dev-le...@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/4OKQ5DARENNMKN7DVX72K46KKWO6PFCQ/
> Code of Conduct: http://python.org/psf/codeofconduct/
>


-- 
--Guido van Rossum (python.org/~guido)
*Pronouns: he/him **(why is my pronoun here?)*

___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@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/IT3A33GXLAMNEMCLQTJSS5KJ7ZUSG633/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] PEP 584 underspecified

[David Mertz]

I know this is late in the cycle to think of this.  But I just realized the
PEP 584 does not say anything about order guarantees.

I think it is safe to assume that existing keys in dictA will not have
order modified by `dictA |= dictB`.  However, the PEP does not state what
order we are given when new keys are added.  I reckon it is a kind of
insertion, so they must occur after the existing keys.  However, stating
explicitly that the MUST  (or alternately MIGHT NOT) be inserted in the
order that dictB has seems worth specifying.

Moreover, the new operator explicitly states that it will flexibly deal
with mapping types other than dict on the right hand side.  So what happens
with:

dictA |= unorderedmapB

I think the "reasonable" belief should be that all new keys will be in some
unspecified order amongst themselves, but all occurring after the old
keys.  I think a sentence or two explicitly indicating what is promised and
what is not would be worthwhile.

>
>-
>
>PEP 584 , Union Operators
>in dict
>
> --
The dead increasingly dominate and strangle both the living and the
not-yet born.  Vampiric capital and undead corporate persons abuse
the lives and control the thoughts of homo faber. Ideas, once born,
become abortifacients against new conceptions.
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@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/4OKQ5DARENNMKN7DVX72K46KKWO6PFCQ/
Code of Conduct: http://python.org/psf/codeofconduct/

[Python-Dev] [RELEASE] Python 3.9.0b1 is now available for testing

[Łukasz Langa]

On behalf of the entire Python development community, and the currently serving 
Python release team in particular, I’m pleased to announce the release of 
Python 3.9.0b1. Get it here:

https://www.python.org/downloads/release/python-390b1/ 


This is a beta preview of Python 3.9

Python 3.9 is still in development. This release, 3.9.0b1, is the first of four 
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.

Call to action

We strongly encourage maintainers of third-party Python projects to test with 
3.9 during the beta phase and report issues found to the Python bug tracker 
 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 (2020-08-10). Our goal is have no ABI changes after beta 4 and 
as few code changes as possible after 3.9.0rc1, the first release candidate. To 
achieve that, it will be extremely important to get as much exposure for 3.9 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.9 series, compared to 3.8

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

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 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 .

(Hey, fellow core developer, if a feature you find important is missing from 
this list, let Łukasz know .)

The next pre-release, the second beta release of Python 3.9, will be 3.9.0b2. 
It is currently scheduled for 2020-06-08.

More resources

Online Documentation 
PEP 596 , 3.9 Release Schedule
Report bugs at https://bugs.python.org .
Help fund Python and its community .
Your friendly release team,
Ned Deily @nad 
Steve Dower @steve.dower 
Łukasz Langa @ambv ___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@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/LQGV4LVIQEOM2HRPSAFXBJKDTEBZ2Z5R/
Code of Conduct: http://python.org/psf/codeofconduct/