On 08. 04. 22 9:51, Inada Naoki wrote:
Thank you, Victor.
I had considered dropping (a) from the PEP. But I keep them because:
* I rushed to write PEP, before 3.11 beta.
* In the "Backward compatibility" section in the PEP, I want to
mention `locale.getencoding()` and `encoding="locale"`
* But they are not fixed in the main branch yet. So I need to include
what needs to be fixed in 3.11 in the PEP.
But for now, we are close to merge `locale.getencoding()`.
And I am afraid merging it before the PEP accepted even though it is
documented in the PEP...
Now I think the best way is:
* Withdraw the PEP submission temporarily.
* Implement `locale.getencoding()` and fix `encoding="locale"` in the
main branch.
* Remove them from the PEP.
* Resubmit the PEP.
That shouldn't be necessary. If you're making these changes anyway, you
can just add a note to the SC request that the 3.11 changes are being
merged now. (I'll just do that myself now!)
Then update the PEP to say "This API was added in Python 3.11" instead
of "will be added".
The SC did ask people to not submit PEPs that still have planned
changes. I think that's because discussing the old version is
essentially a waste of time, and if the change comes as a surprise it's
frustrating.
But if the SC knows about the planned changes, it can adapt -- either
delay its discussions, or just decide to discuss it anyway.
“Don't make *surprise* changes” is the main point, as I see it.
_______________________________________________
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at
https://mail.python.org/archives/list/python-committers@python.org/message/2SYJFQUAQH7BU2LOJG6UKRMWZZZELPXG/
Code of Conduct: https://www.python.org/psf/codeofconduct/
