Hello, a while back we hit a bug with doctest and mock.call that
confused a few people on our team for a while.
I dug into fixing it and made doctest more defensive around
un-unwrappable calls.
I submitted a PR (https://github.com/python/cpython/pull/22981) for an
Issue
From Thomas Wouters, on behalf of and with full support of the Python Steering
Council:
This discussion seems to have died down a little, but I still want to make a
few things clear:
Yes, this is a political decision. Very many decisions are political. The
existence of an open-source project
On Tue, Mar 23, 2021 at 12:02:38PM -0700, Python Steering Council wrote:
From Thomas Wouters, on behalf of and with full support of the Python Steering
Council:
[use of SC power; specifically, PEP-0013.Powers.2: 'Enforce ... code of
conduct']
From PEP 13[^1]
To use its powers, the council
From Thomas Wouters, on behalf of and with full support of the Python Steering
Council:
I’ll post a separate reply about the merits of the decision, but we have to
talk about this post from Steven D’Aprano in particular.
Steven, this reply -- its tone and its message -- are completely
Thanks all! Approved the PR.
Bill
From: Guido van Rossum
Sent: Tuesday, 23 March 2021 14:14
To: codeofd...@gmail.com
Cc: Python-Dev
Subject: Re: [Python-Dev] typo in PEP 636
Sorry, I see Jelle already did this.
https://github.com/python/peps/pull/1891/files
On Tue, Mar 23, 2021
Sorry, I see Jelle already did this.
https://github.com/python/peps/pull/1891/files
On Tue, Mar 23, 2021 at 11:13 AM Guido van Rossum wrote:
> Thanks for your keen eye, Bill!
>
> If you want to, you can submit a PR to the peps repo (
> https://github.com/python/peps) to fix the typo directly.
>
Thanks for your keen eye, Bill!
If you want to, you can submit a PR to the peps repo (
https://github.com/python/peps) to fix the typo directly.
On Tue, Mar 23, 2021 at 10:25 AM wrote:
> Hello,
>
> The GUI section of PEP 636 reads: “It will also requires that the event
> has a position
Submitted a PR to fix it: https://github.com/python/peps/pull/1891. In the
future, feel free to submit a PR directly to the PEP repo for this sort of
minor fix.
El mar, 23 mar 2021 a las 10:22, escribió:
> Hello,
>
> The GUI section of PEP 636 reads: “It will also requires that the event
> has
Hello,
The GUI section of PEP 636 reads: "It will also requires that the event has
a position attribute that matches the (x, y) pattern". It should read "It
will also require that the event has a position attribute that matches the
(x, y) pattern".
Thanks,
Bill
On Tue, Mar 23, 2021 at 9:04 AM Ivan Pozdeev via Python-Dev
wrote:
> Also, how is the now-split-off funcionality to be invoked? Does it require
> two or more imports now, or it's imported on demand when one
> invokes an appropriate test.support entry?
By the way, splitting test.support into
Hi Ivan,
On Tue, Mar 23, 2021 at 9:04 AM Ivan Pozdeev via Python-Dev
wrote:
> I didn't quite get what the big effect is. Saving 30 milliseconds?
I started to dig into this issue while debugging a random crash on AIX
(bpo-40091). A test_threading test using fork randomly crashed on AIX.
I
I didn't quite get what the big effect is. Saving 30 milliseconds?
Also, how is the now-split-off funcionality to be invoked? Does it require two or more imports now, or it's imported on demand when one
invokes an appropriate test.support entry?
On 23.03.2021 4:29, Victor Stinner wrote:
Hi,
12 matches
Mail list logo
