On Fri, Apr 8, 2022 at 6:05 PM Petr Viktorin wrote:
>
>
> 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 i
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
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
On Thu, Apr 7, 2022 at 5:35 AM Inada Naoki wrote:
> I just submitted the PEP 686 to the SC.
> https://github.com/python/steering-council/issues/118
>
> In this PEP, I am proposing:
>
> a. Small improvement for UTF-8 mode in Python 3.11
> b. Make UTF-8 mode default in Python 3.13.
It's easier to a
IMO adding locale.getencoding() to Python 3.11 is not controversial
and is useful even if PEP 686 is rejected. This function was discussed
for 1 year (bpo-43510, bpo-43552, bpo-43557, bpo-47000) and there is
an agreement that there is a need for this function.
> Making `open(path, encoding="locale
Hi, Pablo.
I just submitted the PEP 686 to the SC.
https://github.com/python/steering-council/issues/118
In this PEP, I am proposing:
a. Small improvement for UTF-8 mode in Python 3.11
b. Make UTF-8 mode default in Python 3.13.
(a) is an important change for (b) so I included it in the PEP.
Mor
