Hi, all.
I found .pth file is decoded by the default (i.e. locale-specific) encoding.
https://github.com/python/cpython/blob/0269ce87c9347542c54a653dd78b9f60bb9fa822/Lib/site.py#L173
pth files contain:
* import statements
* paths
For import statement, UTF-8 is the default Python code encoding.
Thank you, SC members, Victor, and Marc.
On Tue, Mar 16, 2021 at 3:49 AM Thomas Wouters wrote:
>
>
> Hi Inada,
>
> Thank you for submitting PEP 624 (Remove Py_UNICODE encoder APIs). The
> Steering Council is happy to accept it, but we do have two conditions. We
> want to make sure that the
Thank you, Council members and all members joined in the long discussion.
On Tue, Mar 16, 2021 at 8:29 AM Guido van Rossum wrote:
>
>>
>> Once the whole stdlib and most of top PyPI projects will be fixed to
>> no longer emit EncodingWarning, I will become safer to opt-in for
>> UTF-8 by default
I am not a Python developer, but I am very interested in this topic. While I
would definitely make use of any additional fields for exceptions as discussed,
it is already possible to find most, if not all of the information discussed in
PEP 473. To give just a concrete example taken from the
On Mon, Mar 15, 2021 at 3:58 PM Victor Stinner wrote:
> Congratulation INADA-san! I'm impressed by your tenacity :-)
>
+1. Great work!
> Last months, I followed your different propositions on
> discuss.python.org to use UTF-8 by default in Python. It's good to see
> the first
Since tweaking the built-in exceptions is so far-reaching, probably at
least discussing each proposed change (one at a time, not 5 at once) would
be the minimum. Otherwise you could do a PEP, but once again you're looking
at a PEP per exception. I think it's really going to come down to how big
of
Congratulation INADA-san! I'm impressed by your tenacity :-)
Last months, I followed your different propositions on
discuss.python.org to use UTF-8 by default in Python. It's good to see
the first non-controversial part being accepted! I hope that this PEP
will help to move towards a world where
Actually, the key part of the new syntax, x[a=b], is not useful for typing,
at least it's not something that's been discussed in the typing-sig at all.
The only part we want is x[*y].
On Mon, Mar 15, 2021 at 3:27 PM Barry Warsaw wrote:
> I think this is really the crux of the rejection: is the
I think this is really the crux of the rejection: is the new syntax being
proposed primarily to support typing, or Python in general? Does it help both,
or is one use case the motivating factor, and the other is just piggybacking on
the syntactic proposal? Quoting from the rejection email:
>
El lun, 15 mar 2021 a las 13:13, Guido van Rossum ()
escribió:
> Let me clarify what the typing-sig folks wanted out of this PEP. We only
> care about adding support for `x[*y]` (including things like `x[a, *b,
> c]`). We'll just update PEP 646 to add that explicitly there and hope that
> PEP 646
Let me clarify what the typing-sig folks wanted out of this PEP. We only
care about adding support for `x[*y]` (including things like `x[a, *b,
c]`). We'll just update PEP 646 to add that explicitly there and hope that
PEP 646 fares better than PEP 637.
To fans of PEP 637 I would call out that
Hi Inada,
Thank you for submitting PEP 624 (Remove Py_UNICODE encoder APIs). The
Steering Council is happy to accept it, but we do have two conditions. We
want to make sure that the documentation is clear on what is deprecated,
and when they are scheduled to be removed. For example,
Hi Inada,
Thank you for submitting PEP 597 (Add optional EncodingWarning). The
Steering Council is happy with the PEP, and hereby accepts it. The SC is of
the opinion that we should move towards making UTF-8 the default encoding,
and this PEP will make it easier to do so, and mitigate some of the
Hi Stefano,
Thank you for submitting PEP 637 (Support for indexing with keyword
arguments). The Steering Council has reviewed the PEP and after careful
consideration, we have decided to reject the PEP. There are a number of
reasons for this, but fundamentally we do not believe the benefit is
The sign up for Python Language Summit is still open but only for 7 more
days!
We received a few more attendee sign ups since last time I posted here, but
we haven't received very many topic proposals yet.
If you've been thinking of proposing a discussion topic to the language
summit, now is the
15 matches
Mail list logo
