On 21 Sep 2020, at 07:26, Abdur-Rahmaan Janhangeer <arj.python@gmail.com> wrote:

Greeting lists,

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.

Backstory:

I quoted V. Stinner in this for PEP 608, 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 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.

Barry





Kind Regards,

Abdur-Rahmaan Janhangeer
github
Mauritius
_______________________________________________
Python-ideas mailing list -- python-ideas@python.org
To unsubscribe send an email to python-ideas-leave@python.org
https://mail.python.org/mailman3/lists/python-ideas.python.org/
Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/MQWM42U3BWLFONQW7JLQHEVDFBMMK3BU/
Code of Conduct: http://python.org/psf/codeofconduct/