Hi, I'd like to revive this thread after what seemed like a decade and see
where this might take us 😃
I like this idea that the OP suggested but I'd like to extend this to all
iterator objects (range_iterators, list_iterators etc.).
📌Idea
Iterables to expose the .__iter__() method in iterable
I ran into a problem which, according to a google search is not that
uncommon:
concurrent.futures ThreadPoolExecutor, installs an exit handler
preventing program exit if any of the jobs it is running is blocked. (Which
might be a surprising behaviour to someone using those).
It is possible to
On Mon, Mar 9, 2020 at 11:18 PM Kyle Stanley wrote:
> We're currently looking into adjusting the current Executor implementation
> (for both TPE and PPE) to not use daemon threads at all for subinterpreter
> compatibility, see https://bugs.python.org/issue39812. Instead of using
> an atexit handl
On Tue, Mar 10, 2020 at 1:04 PM Rhodri James wrote:
> Well, yes. The non-ugly thing would be to make sure your threads are
> well behaved ;-)
>
That is kinda hard to do for the general case, i prefer to have a failsafe.
___
Python-ideas mailing list -
On Wed, Mar 11, 2020 at 3:20 AM Kyle Stanley wrote:
> IIUC, I don't think there's a way that we could reasonably support
> stability for provide any guarantees for spawning or interacting with the
> Executors from a daemon thread. It might even be worth considering to
> explicitly warn or prevent
