Abdur-Rahmaan Janhangeer about | blog github Mauritius
On Mon, Sep 21, 2020 at 11:46 AM Steven D'Aprano firstname.lastname@example.org wrote:
On Mon, Sep 21, 2020 at 11:25:52AM +0400, Abdur-Rahmaan Janhangeer wrote:
How would this work in practice? After a PEP is accepted, are we supposed to go back through all the references to it and change them all to PAP? Do we expect people to search for "PAP 12345" and "PEP 12345" if they are unsure whether it is accepted or not?
For future PEPs. People have to remember that after PEP x you have PEPs and 'PAP's
No, for future PEPs you will still have to look for "PEP x" as well, because they won't be created in the accepted state. So there will be discussion of the PEP under "PEP". Most of the discussion will be prior to acceptance, so most references will be under "PEP" and hardly anything under "PAP".
By future PEPs i mean future PEP naming, Not about PEP referencing
If you don't look it up, knowing that it is accepted doesn't tell you much. Why would I care that PEP 12345 is accepted, if I don't know what PEP 12345 is about?
When someone talks about PEP 12345, they give details etc e.g:
PEP 345 talks about introducing type this and that
unless you are robots, the person will give some background info but the above though not saying anything wrong does not tell whether or not it's an accepted PEP, whether you can form further opinions or not
I would expect that, if you know the context of the discussion and the nature of the PEP, anyone with a good knowledge of Python should be able to make a good guess of whether it was accepted or not.
I quote the first mail:
... you need to be a PEP historian
Not always. You often just need to know Python.
It depends on what you mean by know
Surely you can tell the difference between features that are in the existing language like nested scopes, the walrus operator, or the secrets module, and features that aren't, like the directive operator, the list.uniq method, and int for loops, without looking them up?
In my opinion, "accepted versus not accepted" is one of the least important and least informative parts of a PEP.
By accepted it means the PEP made a significant change in the Python language.