Hi,
I think it would be very helpful to have an additional argument (cancel for
example) added to Executor.shutdown that cancels all pending futures submitted
to the executor. Then context manager would gain the ability to abort all
futures incase of a exception, additionally this would also
Ideally, we'd have a functional package manager: one that can delete
binaries when disk space is running low, and recompiles from sources when
the binary is needed again. It could store Python 2 as a series of diffs
against Python 3.
On Thu, Jan 2, 2020, 2:22 AM Abdur-Rahmaan Janhangeer
wrote:
On Thu, Jan 2, 2020, at 13:22, Dan Sommers wrote:
> What about "if except" (any time I can eliminate a "not," that's a good
> thing):
wait, is this meant to be for the doesn't-throw case or does-throw? how are we
eliminating the not?
> if except x:
> y
>
> which could even leave
On 1/2/20 12:55 PM, Andrew Barnert via Python-ideas wrote:
> On Jan 2, 2020, at 06:32, Random832 wrote:
>> Mainly, you had mentioned you felt like "if try" had a 'smell' to it
>> but couldn't figure out what it is, and I was trying help identify
>> that, and... well, after thinking about it
On Jan 2, 2020, at 06:32, Random832 wrote:
>
> Mainly, you had mentioned you felt like "if try" had a 'smell' to it but
> couldn't figure out what it is, and I was trying help identify that, and...
> well, after thinking about it more, I realized - "if try" may not have many
> uses, but "if
On Wed, Jan 1, 2020, at 21:49, Andrew Barnert wrote:
> On Jan 1, 2020, at 13:23, Random832 wrote:
> >
> > Neither of these constructs seems to be particularly useful outside the
> > other one,
>
> Yes, and you already quoted me as saying that.
I think I read "not proposing them separately" as
