[Python-Dev] Making the status of Provisional PEPs clearer
Nick Coghlan
ncoghlan at gmail.com
Sat Jul 7 23:29:39 EDT 2018
More information about the Python-Dev mailing list
Sat Jul 7 23:29:39 EDT 2018
- Previous message (by thread): [Python-Dev] Making the status of Provisional PEPs clearer
- Next message (by thread): [Python-Dev] Making the status of Provisional PEPs clearer
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 8 July 2018 at 12:48, Guido van Rossum <guido at python.org> wrote: > Should we update some PEPs with the new status? E.g. PEP 484. Aye, 3 PEPs were given the new status as part of the commit: - 484 (type hinting syntax) - 518 (pyproject.toml/[build-system].requires) - 517 (pyproject.toml/[build-system].backend) Checking the other Accepted PEPs, it looks like a few of them need to be marked Final now that 3.7 has been released, but I don't believe any of them are Provisional. Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message (by thread): [Python-Dev] Making the status of Provisional PEPs clearer
- Next message (by thread): [Python-Dev] Making the status of Provisional PEPs clearer
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list