This is my favourite version of the issue:
е = lambda е, e: е if е > e else e
print(е(2, 1), е(1, 2)) # python 3 outputs: 2 2
https://twitter.com/stestagg/status/685239650064162820?s=21
Steve
On Sat, 13 Nov 2021 at 22:05, wrote:
> I’ve not been following the thread, but Steve
On Mon, Apr 26, 2021 at 10:31 PM Brett Cannon wrote:
>
>
> On Mon, Apr 26, 2021 at 9:37 AM Baptiste Carvello <
> devel2...@baptiste-carvello.net> wrote:
>
>> Hi,
>>
>> sorry for being late to the party, but I may not be the only one
>> wondering…
>>
>> Le 14/04/2021 à 20:56, Barry Warsaw a écrit
Thanks for the response!
No. It has been discussed by the Steering Council as you can see in the
> February update:
> https://github.com/python/steering-council/blob/main/updates/2021-02-steering-council-update.md
>
>
Ok, great, I assume the missing bits will be coming in the March update
Steve
_
Hi
I would be great to read the impact analysis for this change, and
understand who the identified impacted parties are, and what the plan is to
notify them and help them update within this timescale.
Has this analysis been published anywhere? I know there are lots of places
where discussions/doc
On Tue, Feb 23, 2021 at 11:00 PM Irit Katriel
wrote:
>
> Hi Steve,
>
> Thank you for trying out the implementation. Please do let me know about
> bugs you find.
>
>
Thanks you for your response! It seems I had missed the (now) obvious
naked exception wrapping logic. Apologies for adding noise t
This pep sounded kinda scary to me, so I wanted to try it out.
The reference implementation appears to have some bugs in it (around
reraise star) , so it's not entirely clear what the expected behavior is
supposed to be, but by checking out ffc493b5 I got some OK results.
I had a look at the temp
On Fri, 19 Feb 2021 at 22:50, Christian Heimes wrote:
> On 19/02/2021 23.22, Stestagg wrote:
> > The thing that stood out from this conversation, for me, is: Releases
> > are too hard, and there’s a risk of not having enough volunteers as a
> > result.
> >
>
The thing that stood out from this conversation, for me, is: Releases are
too hard, and there’s a risk of not having enough volunteers as a result.
How hard is it to fix that?
Steve
On Fri, 19 Feb 2021 at 22:05, Terry Reedy wrote:
> On 2/19/2021 5:11 AM, Michał Górny wrote:
> > On Thu, 2021-02
Hi Robin
It would be ideal if you could please create a new issue here:
https://bugs.python.org/
Thanks
Steve
On Sun, Jan 17, 2021 at 12:53 PM Robin Becker wrote:
> Not sure if this is where I should report, but I have a segfault in
> reportlab userguide creation with 3.10a4. I am
> getting t
I've raised: https://bugs.python.org/issue42899.
The triggering commit was: c71581c7a4192e6ba9a79eccc583aaadab300efa
bpo-42615: Delete redundant jump instructions that only bypass empty blocks
(GH-23733)
On Mon, Jan 11, 2021 at 8:04 PM Guido van Rossum wrote:
> All that said (I agree it's s
For what it's worth, this recent issue: https://bugs.python.org/issue42762
is somewhat related to the non-async aspect of 533. (generator func getting
closed during __del__ and causing odd side-effects at seemingly random
points in the execution flow)
The example code provided in that issue is con
11 matches
Mail list logo
