Hmm, interesting thought! I'll try that out.
Thanks!
On Fri, Jun 26, 2020, 01:51 Antoine Pitrou wrote:
> On Thu, 25 Jun 2020 18:32:48 -0700
> Yonatan Zunger via Python-ideas
> wrote:
> >
> > So that's an example of why you might find yourself in such a situation
> in
> > userland. And overall,
On Thu, 25 Jun 2020 18:32:48 -0700
Yonatan Zunger via Python-ideas
wrote:
>
> So that's an example of why you might find yourself in such a situation in
> userland. And overall, Python's signal handling mechanism is pretty good;
> it's *way* nicer than having to deal with it in C, since signal ha
Oh, that's definitely part of the problem, but that is *far* beyond my
ability to fix. Right now I'm still working on getting its owners to do
things like "could you please log somewhere when you kill jobs, and maybe
even indicate why the job was killed?".
The main time that signals show up in lif
On Thu, Jun 25, 2020 at 5:09 PM Yonatan Zunger via Python-ideas <
python-ideas@python.org> wrote:
> Hey everyone,
>
> I've been developing code which (alas) needs to operate in a runtime
> environment which is quite *enthusiastic* about sending SIGTERMs and the
> like, and where there are critical
Absolutely, but I figured the natural thing to expose from the C API was a
very minimal function, and then put a context manager in the Python layer.
The actual context manager implementation I would use would be a bit
smarter than a bare set/reset -- it would use an unbounded semaphore and
only u
On 2020-06-25 21:05, Yonatan Zunger via Python-ideas wrote:
Hey everyone,
I've been developing code which (alas) needs to operate in a runtime
environment which is quite /enthusiastic/ about sending SIGTERMs and the
like, and where there are critical short sections of code that, if
interrupte
