On Sun, 10 Jan 2021, 2:55 am Paul Moore, wrote:
> On Sat, 9 Jan 2021 at 14:54, Nick Coghlan wrote:
>
> [...]
> > And I've already said I'd be fine with making the colon mandatory if the
> SC share that view.
>
> So the response to my comment that omitting the colon makes it hard to
> see that it
On Sat, 9 Jan 2021 at 14:54, Nick Coghlan wrote:
[...]
> And I've already said I'd be fine with making the colon mandatory if the SC
> share that view.
So the response to my comment that omitting the colon makes it hard to
see that it's a dictionary unpacking is either "don't use that form if
y
Hello,
On Sun, 10 Jan 2021 01:42:25 +1000
Nick Coghlan wrote:
> On Sat, 9 Jan 2021, 8:50 pm Paul Sokolovsky,
> wrote:
>
> > >
> > > The key difference relative to PEP 634 is that even when the code
> > > author uses the shorthand form, *readers* will still get at least
> > > the "as" keyword a
On Sat, 9 Jan 2021, 8:50 pm Paul Sokolovsky, wrote:
> >
> > The key difference relative to PEP 634 is that even when the code
> > author uses the shorthand form, *readers* will still get at least the
> > "as" keyword as a prompt,
>
> Ok, so let's summarize the alternatives:
>
> 1. PEP634, which s
On Sun, 10 Jan 2021, 12:54 am Nick Coghlan, wrote:
>
>
> On Sun, 10 Jan 2021, 12:22 am Paul Moore, wrote:
>
>> On Sat, 9 Jan 2021 at 13:53, Antoine Pitrou wrote:
>>
>>
>> The dictionary destructuring can act as an example. We know Nick's
>> position:
>>
>> case {"text": message, "color": c}
On Sun, 10 Jan 2021, 12:22 am Paul Moore, wrote:
> On Sat, 9 Jan 2021 at 13:53, Antoine Pitrou wrote:
>
> > So, opposing Nick's proposal on the basis that it "looks like a set" is
> > just like opposing set literals on the basis they they "look like a
> > dict".
>
> That's not what I was doing (
Hello,
On Sat, 9 Jan 2021 14:49:19 +0100
Antoine Pitrou wrote:
> On Sat, 9 Jan 2021 12:17:32 +
> Paul Moore wrote:
>
> > On Sat, 9 Jan 2021 at 10:52, Paul Sokolovsky
> > wrote:
> > > > case {"host" as host, "port" as port}:
> > >
> > > There're 2 obvious problems with it:
> > >
> >
Le 09/01/2021 à 15:18, Paul Moore a écrit :
>
> But the PEP 642 form:
>
> case {"text" as message, "color" as c}:
>
> is essentially identical except for using "as" rather than a colon. My view
> is:
>
> 1. Nowhere else in Python does "as" indicate a dictionary, and braces
> alone don't (
On Sat, 9 Jan 2021 at 13:53, Antoine Pitrou wrote:
> So, opposing Nick's proposal on the basis that it "looks like a set" is
> just like opposing set literals on the basis they they "look like a
> dict".
That's not what I was doing (I can't comment on what Paul S intended,
though). My position i
On Sat, 9 Jan 2021 12:17:32 +
Paul Moore wrote:
> On Sat, 9 Jan 2021 at 10:52, Paul Sokolovsky wrote:
> > > case {"host" as host, "port" as port}:
> >
> > There're 2 obvious problems with it:
> >
> > a) In Python, {} with things inside it, but no ":" inside it, is a set,
> > set.
> > b) Ev
On 1/8/2021 2:50 PM, Chris Barker via Python-Dev wrote:
If there are other common types this helps with, sure. But for numpy, as pointed out elsewhere in this thread, it would still fail for numpy arrays of > 1
dimension.
Personally I think this is really an issue with the structure of unitest
On Sat, 9 Jan 2021 at 10:52, Paul Sokolovsky wrote:
> > case {"host" as host, "port" as port}:
>
> There're 2 obvious problems with it:
>
> a) In Python, {} with things inside it, but no ":" inside it, is a set,
> set.
> b) Everywhere else in Python, thing on the left of "as" gets into
> thing on
> On 8 Jan 2021, at 20:38, Chris Barker via Python-Dev
> wrote:
>
> Sorry if I'm out of the loop here, but with Apple's new chip coming out, we
> need new a build configuration (which I think has already been started, if
> not done).
>
> Perhaps we could take this opportunity to better modu
Hello,
On Sat, 9 Jan 2021 12:27:45 +1000
Nick Coghlan wrote:
> On Sat, 9 Jan 2021, 7:07 am Joseph Martinot-Lagarde,
> wrote:
>
> > Paul Sokolovsky wrote:
> > > Hello,
> > > On Tue, 5 Jan 2021 20:37:27 +1000
> > > Nick Coghlan ncogh...@gmail.com wrote:
> > > > object(host=as host, port=as p
On Sat, 9 Jan 2021 02:02:17 +0100
Victor Stinner wrote:
>
> It's an hard problem and I don't see any simple/obvious solution right
> now, except of *workarounds* that I dislike. Maybe the only good
> solution is to fix all heap types, one by one.
Ok. Why are we adding heap types to the stdlib ex
15 matches
Mail list logo
