public way to disable atexit callback for AddThreadSelectorEventLoop about tornado HOT 3 CLOSED

Try the recent changes in the master branch (specifically #3272). This will shut down the selector thread cleanly (without leaving it for atexit) as long as you're using asyncio.run.

I wonder if the atexit hook is even still necessary. As the comment says, I was never able to reproduce or understand it properly (it doesn't make sense for this to be necessary in a daemon thread). Now that we have a cleaner shutdown method, I'm not sure we really need the atexit hook as a fallback (but because it's so poorly understood I'm not confident we can remove it either).

from tornado.

Try the recent changes in the master branch (specifically #3272). This will shut down the selector thread cleanly (without leaving it for atexit) as long as you're using asyncio.run.

I don't expect this to work because my asyncio.run call needs to outlive the atexit callbacks

from tornado.

Ah, OK. So the existing changes won't help you and we either need to get rid of the atexit callback or give you a way to opt out. I'm leaning towards the former; it's really hard for a library to safely use an atexit callback and it doesn't feel necessary anymore. But we'll see if CI is happy when I make the change...

from tornado.