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 n
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 the