On Tue, Feb 2, 2021 at 8:16 PM Victor Stinner wrote:
>
> > > I understand that encoding=locale.get_locale_encoding() would be
> > > different from encoding="locale":
> > > encoding=locale.get_locale_encoding() doesn't call
> > > os.device_encoding(), right?
> > >
> >
> > Yes.
>
> Would it be
Hello,
Everyone knows how hard to find a compelling usecase for the assignment
expression operator (":=", colloquially "walrus operator").
https://www.python.org/dev/peps/pep-0572/ examples never felt
compelling and we all remember the split it caused.
I finally found a usecase where *not* using
We have examined every possible permutation already, I think this would be
a distraction to pursue.
On Thu, Feb 4, 2021 at 04:20 Walter Dörwald wrote:
> On 2 Feb 2021, at 12:36, Stefano Borini wrote:
>
> Hi all,
>
> I would like to request feedback by python-dev on the current
> implementation
Breaks are good. Looking forward to the next prototype!
On Thu, Feb 4, 2021 at 10:45 AM Larry Hastings wrote:
>
> After working on it and stressing out about it for some months, I decided
> to take a break and scratch some other itches. I'll return to PEP 649
> soon, and I have every intention
After working on it and stressing out about it for some months, I
decided to take a break and scratch some other itches. I'll return to
PEP 649 soon, and I have every intention of having the PEP done and the
prototype done well in advance of 3.10b1--worry not.
Thanks for checking in,
Hi Larry,
Can you give us a status update for your PEP 649? I don't recall reading
anything about it in the past few weeks. I am super excited about this
solution to the problem (even if there are a few issues to work through)
and I think it will provide better backwards compatibility than the
On Tue, Feb 2, 2021 at 8:40 PM Inada Naoki wrote:
>
> On Tue, Feb 2, 2021 at 7:37 PM M.-A. Lemburg wrote:
> >
> > BTW: I don't understand this comment:
> > "They are inefficient on platforms wchar_t* is UTF-16. It is because
> > built-in codecs supports only UCS-1, UCS-2, and UCS-4 input."
> >
>
On 2 Feb 2021, at 12:36, Stefano Borini wrote:
Hi all,
I would like to request feedback by python-dev on the current
implementation of PEP 637 - Support for indexing with keyword
arguments.
https://www.python.org/dev/peps/pep-0637/
The PEP is ready for SC submission and it has a prototype
Hi Sven,
On 04/02/2021 9:06 am, Sven R. Kunze wrote:
On 03.02.21 23:37, Nick Coghlan wrote:
No, PEP 558 doesn't remove it, it enhances it to be a live view of the
frame state instead of an inconsistently updated snapshot.
As long as it is possible to **write** to existing keys to **add
On Thu, 4 Feb 2021 at 10:34, Stefano Borini wrote:
> I'd focus only on the use of the feature "from the outside", that is,
> using the indexing operation as a common user.
> For implementing the dunders, it's an advanced feature and it's
> unlikely to be discussed during basic teaching sessions.
On Thu, 4 Feb 2021 at 01:21, Petr Viktorin wrote:
> The PEP does lack a "How to teach" section.
I can add it tonight, and I think it would clarify some corner cases
to make them more natural.
Do you have something specific you are concerned about, when it comes
to "teachability" (stress point,
On 03.02.21 23:37, Nick Coghlan wrote:
No, PEP 558 doesn't remove it, it enhances it to be a live view of the
frame state instead of an inconsistently updated snapshot.
As long as it is possible to **write** to existing keys to **add new
keys** to frame.f_locals, I am actually quite happy.
12 matches
Mail list logo
