On 21 Sep 2020, at 07:26, Abdur-Rahmaan Janhangeer firstname.lastname@example.org wrote:
I am thinking of proposing to name accepted PEPs as PAPs namely: Python Accepted Proposals.
Hence if we say PAP8 we know it's an accepted proposal.
I quoted V. Stinner in this https://dev.to/abdurrahmaanj/the-zen-of-python-as-related-by-masters-1p9i for PEP 608 https://www.python.org/dev/peps/pep-0608/, he told me by the way it was not accepted. This got me thinking that to know accepted peps on reading or hearing of it without seeing the status, you need to be a PEP historian. But, if on the other hand you see PEP 0608, you instantly know it has not been accepted and when you hear of PAP 561 you know it is an accepted PEP
I know that PEPs have different status as enumerated here https://www.python.org/dev/peps/ but at least such a naming would make a clear distinction.
Curious to hear your thoughts ^^
This is like RFC that can be draft, accepted or rejected. RFC's have not needed to change there names. I'd rather not have PEP's change there names either.
As you say there is a Status in the PEP that is clear.
I see that the RFC docs have more info like "obsoleted by" and "updated by" info.
I work with RFC's all the time an appreciate the forward and backward references. So if I'm working on code that refers to an RFC I can check to see if it is still current for example.
Abdur-Rahmaan Janhangeer about https://compileralchemy.github.io/ | blog https://abdur-rahmaanj.github.io/ github https://github.com/Abdur-RahmaanJ Mauritius _______________________________________________ Python-ideas mailing list -- email@example.com To unsubscribe send an email to firstname.lastname@example.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://email@example.com/message/MQWM42... Code of Conduct: http://python.org/psf/codeofconduct/