Hi, Stanley:
Thanks for your comments.
Almost all the patches are simple compatibility patch. But the subprocess
module is an exception. Like windows, VxWorks have no fork/exec API provided.
Instead, VxWorks uses rtpSpawn() to spawn a new process. So we have to
implement VxWorks’ own
What exactly does the PR involve? Is it a relatively simple compatibility
patch or something that adds significant amounts of platform-specific code?
The former can be reviewed (and potentially merged) by any core dev
knowledgeable in the areas being changed, but the latter requires long-term
On Wed, Aug 5, 2020 at 8:14 PM Larry Hastings wrote:
> It's interesting to consider how C# did it. For example, at the same time
> they added pattern matching, they also added "discards", which are
> (undeclared-only?) variables whose name starts with '_' and whose value is
> never retained.
It's interesting to consider how C# did it. For example, at the same
time they added pattern matching, they also added "discards", which are
(undeclared-only?) variables whose name starts with '_' and whose value
is never retained. I'm not sure, but I believe the language previously
Off the top of my head for recently happened and fairly mainstream language:
C# added it in 8.0
https://docs.microsoft.com/en-us/archive/msdn-magazine/2019/may/csharp-8-0-pattern-matching-in-csharp-8-0
On Wed, Aug 5, 2020 at 3:33 PM Luciano Ramalho wrote:
> On Tue, Aug 4, 2020 at 1:37 PM Tobias
On Tue, Aug 4, 2020 at 1:37 PM Tobias Kohn wrote:
> And experience from other programming languages who took the leap to having
> pattern matching shows that it quickly becomes a quite intuitive and easy to
> use feature.
The languages I know about that have pattern matching had it from the
PEP 622 is already on the SC’s agenda for review.
-Barry
> On Aug 5, 2020, at 09:47, Ethan Furman wrote:
>
> On 7/30/20 8:35 AM, Rob Cliffe via Python-Dev wrote:
>
>> The debate is still going on as to whether "capture" variables should be
>> marked...
> I don't think the PEP authors are
On Wed, Aug 5, 2020 at 9:48 AM Ethan Furman wrote:
> I don't think the PEP authors are debating it any more. Quite frankly,
> I wish they would present to the SC and get accepted so we can get
> Pattern Matching added to 3.10. :)
>
We did, a few weeks ago, and the SC is already reviewing it.
Hi Carol,
I was wondering if you've been able to set up the workgroup yet? I'd certainly
be interested in participating the there's an opportunity.
Stay safe
Dom
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to
> On 4 Aug 2020, at 14:38, Koos Zevenhoven wrote:
>
> Hi everyone,
>
> [ … analysis of design goals and possible solutions, including … ]
>
> Point3D(x=pi, y=SIX, z=value)
It suddenly struck me that
Point3D(x=pi, y=SIX, z into value)
would quite accurately describe what is being
On Wed, 5 Aug 2020 09:47:30 -0700
Ethan Furman wrote:
> On 7/30/20 8:35 AM, Rob Cliffe via Python-Dev wrote:
>
> > The debate is still going on as to whether "capture" variables should be
> > marked...
> I don't think the PEP authors are debating it any more.
That would be a pity.
On 7/30/20 8:35 AM, Rob Cliffe via Python-Dev wrote:
The debate is still going on as to whether "capture" variables should be
marked...
I don't think the PEP authors are debating it any more. Quite frankly,
I wish they would present to the SC and get accepted so we can get
Pattern Matching
Hi, Python developers:
Anyone interested in PR review and merging for VxWorks RTOS? We can give a
proper pay for that. Contact me if you have interest.
Thanks,
Peixing
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email
On 03/08/2020 17:37, MRAB wrote:
[snip]
A thought occurred to me. By default, the current rules of the PEP
could apply, but why not allow prefixing with "as" for a capture and
"is" for a value?
Yes, I know, comparison of the values is not by identity, but "is" is
a short keyword that
Welcome to python-dev, Rik! Of course you can email to this list.
On 30/07/2020 14:30, Rik de Kort via Python-Dev wrote:
I think adding the Walrus operator is trying to solve a problem that
doesn't exist. Compare the example from the PEP:
[snip]
case (x, y, z):
[snip]
To
15 matches
Mail list logo
