PEP 784: Mark as Accepted #4387
Conversation
As requested by the Steering Council
| documentation for existing modules will be updated to reference the new names | ||
| as well. |
There was a problem hiding this comment.
Do the new names now become canonical? The PEP should take a position.
There was a problem hiding this comment.
I think yes the new names should become canonical. Let's see what other SC members think.
There was a problem hiding this comment.
The intent is for them to become canonical as that is why the compression namespaces is useful. I expect we may iterate on how exactly to present this in our docs outside the PEP.
As far as the text in the PEP goes adding something along the lines of:
"The use of the new compression names will be promoted over the original top level module names in the Python documentation when the users minimum Python version support requirements makes that feasible."
There was a problem hiding this comment.
I added a sentence about this in 53ab0b5. Not sure if I should be stronger in my wording but hopefully that clearly makes a stance.
There was a problem hiding this comment.
Oh, my page was open from last night and I missed Greg's comment. I'll include that text.
There was a problem hiding this comment.
Added in 9d58ebc, I made a slight edit to the sentence to clarify, hopefully that's ok!
|
(adding the label as this PR requires governance approval) |
Co-authored-by: Barry Warsaw <barry@python.org>
emmatyping
changed the title
AA-Turner
changed the title
Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
Co-authored-by: "Gregory P. Smith" <greg@krypto.org>
Discussions-TothreadPEP 123: Mark as Accepted)Statuschanged toAccepted/RejectedResolutionfield points directly to SC/PEP Delegate official acceptance/rejected post, including the date (e.g.`01-Jan-2000 <https://discuss.python.org/t/12345/100>`__)Discussions-To,Post-HistoryandPython-Versionup to dateI removed any references to removal or deprecation of the existing modules other than to say that it is left to a future decision as part of the Backwards Compatibility section.
At the behest of Barry, cc'ing @python/steering-council to review the exact language.
📚 Documentation preview 📚: https://pep-previews--4387.org.readthedocs.build/