[issue39232] asyncio crashes when tearing down the proactor event loop

2021-04-13 Thread Michael Hall
Change by Michael Hall : -- versions: +Python 3.10, Python 3.9 ___ Python tracker <https://bugs.python.org/issue39232> ___ ___ Python-bugs-list mailing list Unsub

[issue37373] Configuration of windows event loop for libraries

2020-02-17 Thread Michael Hall
Change by Michael Hall : -- nosy: +mikeshardmind ___ Python tracker <https://bugs.python.org/issue37373> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39232] asyncio crashes when tearing down the proactor event loop

2020-02-17 Thread Michael Hall
Michael Hall added the comment: Linking out to a real-world example where this still manages to happen after running the event loop for an entire 2 seconds waiting for transports to close themselves after finishing everything else: https://github.com/Cog-Creators/Red-DiscordBot/issues/3560

[issue39651] Exceptions raised by EventLoop.call_soon_threadsafe

2020-02-17 Thread Michael Hall
Change by Michael Hall : -- nosy: +mikeshardmind ___ Python tracker <https://bugs.python.org/issue39651> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39232] asyncio crashes when tearing down the proactor event loop

2020-01-07 Thread Michael Hall
Michael Hall added the comment: I don't know if it would be feasible to add this to asyncio, but having a way to mark a resource as needing to be deterministically cleaned up at loop close could probably solve this as well as the underlying reasons why the transports are leaning on __

[issue39232] asyncio crashes when tearing down the proactor event loop

2020-01-06 Thread Michael Hall
New submission from Michael Hall : When using asyncio.run for an asynchronous application utilizing ssl, on windows using the proactor event loop the application crashes when the loop is closed, completely skipping a finally block in the process. This appears to be due to a __del__ method on

[issue12738] Bug in multiprocessing.JoinableQueue() implementation on Ubuntu 11.04

2011-08-14 Thread Michael Hall
Michael Hall added the comment: I tried switching from joining on the work_queue to just joining on the individual child processes, and it seems to work now. Weird. Anyway, it'd be nice to see the JoinableQueue fixed, but it's not pressin

[issue12738] Bug in multiprocessing.JoinableQueue() implementation on Ubuntu 11.04

2011-08-12 Thread Michael Hall
Michael Hall added the comment: Okay, I have attached the code I've been using. Don't worry about what it does (it's a biology thing), but just follow these steps: 1. Make sure you have numpy and scipy installed. 2. Extract the zip file. 3. Run it with ./svm_main.py te

[issue12738] Bug in multiprocessing.JoinableQueue() implementation on Ubuntu 11.04

2011-08-11 Thread Michael Hall
Michael Hall added the comment: Edit: Sorry, I should have been more clear. The hang occurs after the first child process exits, at which point all four children become zombies (none of the others exit, they just zombify immediately), and the main process sits there waiting forever for the

[issue12738] Bug in multiprocessing.JoinableQueue() implementation on Ubuntu 11.04

2011-08-11 Thread Michael Hall
New submission from Michael Hall : I recently switched to Ubuntu 11.04 from OpenSUSE 11.4, and when I go to run a project I coded a couple days ago under OpenSUSE using the multiprocessing library, it hangs when it did not under OpenSUSE. Specifically, I am using two queues, work_queue from