
On Sat, Apr 18, 2020 at 6:30 AM <oliveira.rodrigo.m@gmail.com> wrote:
I do wish to carry on with writing a PEP with your help guys. What's the next step?
Your primary reference is here: https://www.python.org/dev/peps/pep-0001/#pep-workflow Since you have a sponsor, the next step is to fork the PEPs repo on GitHub and start writing PEP 9999 (the standard placeholder number). You'll find PEP 12 helpful here: https://www.python.org/dev/peps/pep-0012/ Once you've done some keyboard hammering and have yourself a PEP, create a GitHub pull request to propose it for inclusion. At that point, you'll be assigned a PEP number and can both rename your file and change its headers accordingly. And after that, post your PEP to python-ideas and let the bikeshedding commence! I mean, continue! Err, resume with full speed? Something like that anyhow! ChrisA