Ned Batchelder writes:
> I feel like we are missing a key element of Riccardo's point:
> "without editorial guidance." Changes are being made without
> first having an agreement about what the tutorial should be.
That's really unfortunate. But there also ought to be an editorial
activity,
Jim J. Jewett writes:
> I *hope* this was a typo! If
>
> case Point(x=a, y=b):
>
> assigns to a and b (instead of x and y, as in a normal call), then
> that is ... going to be very easy for me to forget, and to miss
> even when I'm aware of it.
I don't argue with your main point
But Point(x as a) already has a meaning in PEP 634; it’s a positional
argument captured in x *and* in a. (Previously spelled as Point(a := x).
The phrase ‘as a’ can be added after any pattern to *also* capture it in
‘a’. More typically used as e.g.‘Pattern(x, y) as p’, which captures the
first two
On Sun, Nov 15, 2020 at 1:56 AM Chris Angelico wrote:
> On Sun, Nov 15, 2020 at 4:28 PM Kyle Stanley wrote:
> >
> > FWIW, I'd like to add my +1 to usage of "as" for spelling class capture
> patterns. This is by far the clearest and easiest to read form I've seen
> thus far, and I suspect that
On Sun, Nov 15, 2020 at 4:28 PM Kyle Stanley wrote:
>
> FWIW, I'd like to add my +1 to usage of "as" for spelling class capture
> patterns. This is by far the clearest and easiest to read form I've seen thus
> far, and I suspect that it would be the easiest to explain to users already
>
On Sat, Nov 14, 2020 at 7:54 AM Nick Coghlan wrote:
> On Sat, 14 Nov 2020 at 09:51, Greg Ewing
> wrote:
> >
> > On 14/11/20 7:45 am, Brandt Bucher wrote:
> > > with (using your own syntactic flavor):
> > > ```
> > > case >first, *>middle, >last:
> > > rebuilt = first, *middle, last
> > >
Hello,
On Fri, 13 Nov 2020 18:45:55 -
"Brandt Bucher" wrote:
> Paul Sokolovsky wrote:
> > Use punctuation ("sigils") to mark as-binding terms. This choice
> > still seems to be under-considered. (As in: it doesn't seem like
> > many people, including the PEP authors, tried to say "indeed,
I very much second this opinion
/Christian
On Sat, 14 Nov 2020, 15.16 Joao S. O. Bueno, wrote:
>
>
> On Sat, 14 Nov 2020 at 10:16, Nick Coghlan wrote:
>
>> On Fri, 13 Nov 2020 at 09:39, David Mertz wrote:
>> >
>> > I have read a great deal of discussion on the pattern matching PEPs and
>>
On Sat, 14 Nov 2020 at 10:16, Nick Coghlan wrote:
> On Fri, 13 Nov 2020 at 09:39, David Mertz wrote:
> >
> > I have read a great deal of discussion on the pattern matching PEPs and
> less formal discussions. It is possible I have overlooked some post in all
> of that, of course.
> >
> > ...
On 11/9/20 2:25 PM, Raymond Hettinger wrote:
On Nov 7, 2020, at 9:51 AM, Riccardo Polignieri via Python-Dev
wrote:
My concern here is that if you start removing or simplifying some
"too-difficult-for-a-tutorial" bits of information on an occasional basis, and
without too much scrutiny or
On Wed, 11 Nov 2020 at 09:59, Victor Stinner wrote:
>
> Hi,
>
> If you embed Python in Python, I would like your opinion on
> https://bugs.python.org/issue42260 issue which adds a way to configure
> the Python initialization in Python.
>
> I'm looking for feedback from people who embed Python and
I think when Riccardo said "The PEPs are the worst," he meant that PEPs
do not work well as documentation for features, because it was not their
purpose. PEPs are designed to be proposals, and then summaries of
decisions. I agree with him that linking to PEPs should be for
supporting
On Fri, 13 Nov 2020 at 09:39, David Mertz wrote:
>
> I have read a great deal of discussion on the pattern matching PEPs and less
> formal discussions. It is possible I have overlooked some post in all of
> that, of course.
>
> ... OK, just saw Guido's "wait for new SC" comment, which I
On Sat, 14 Nov 2020 at 09:51, Greg Ewing wrote:
>
> On 14/11/20 7:45 am, Brandt Bucher wrote:
> > with (using your own syntactic flavor):
> > ```
> > case >first, *>middle, >last:
> > rebuilt = first, *middle, last
> > case {"key": >value, **>rest}:
> > rebuilt = {"key": value, **rest}
On Sat, 14 Nov 2020 at 07:55, Joao S. O. Bueno wrote:
> On Fri, 13 Nov 2020 at 17:36, Jim J. Jewett wrote:
>>
>> I *hope* this was a typo! If
>>
>> case Point(x=a, y=b):
>>
>> assigns to a and b (instead of x and y, as in a normal call), then that is
>> ... going to be very easy for me to
On Sat, 14 Nov 2020 at 01:59, Baptiste Carvello
wrote:
>
> Hi,
>
> Le 12/11/2020 à 18:55, Guido van Rossum a écrit :
> > The position of PEP 622/634/535/636 authors is clear:
>
> well, let me first emphasize that I did *not* mean to reopen the
> discussion on those PEPs, which explain and discuss
Hello,
On Thu, 12 Nov 2020 19:38:38 -0400
David Mertz wrote:
[]
> One idea that I cannot recall seeing, but that seems to make sense to
> me and fit with Python's feel is using a WORD to distinguish between a
> variable value and a binding target. That is, instead of a special
> case
On Fri., 13 Nov. 2020, 4:01 am Guido van Rossum, wrote:
> The position of PEP 622/634/535/636 authors is clear: we see this as a
> necessary feature to support using enums (e.g. Color.RED) or constants
> defined in other modules (e.g. re.I) when simple switch functionality is
> being migrated
18 matches
Mail list logo
