[issue32082] atexit module: allow getting/setting list of handlers directly

Irit Katriel added the comment: Yes, I agree this should be closed as a duplicate of issue17186. The shortcut for updating the list of handlers is not really necessary because the API already allows you to do this. -- resolution: -> duplicate stage: -> resolved status: open -> clos

[issue32082] atexit module: allow getting/setting list of handlers directly

Mark Dickinson added the comment: Thanks, Irit. Should we close this issue as a duplicate? It's not identical (being able to modify the list of handlers versus just being able to inspect it), but it's pretty close. -- ___ Python tracker

[issue32082] atexit module: allow getting/setting list of handlers directly

Irit Katriel added the comment: See also issue17186. -- nosy: +iritkatriel ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue32082] atexit module: allow getting/setting list of handlers directly

Mark Dickinson added the comment: You say "for testing purposes only", but I'd add "for debugging" to the list of use-cases, having just spent a few hours trying to understand why I was getting a particular PySide2 "Internal C++ object already deleted." exception under Python 3.6 but not und

[issue32082] atexit module: allow getting/setting list of handlers directly

Change by Xtrem532 : -- nosy: +Xtrem532 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.o

[issue32082] atexit module: allow getting/setting list of handlers directly

Christopher Hunt added the comment: Updated link to workaround referenced in the original issue: https://github.com/sagemath/sage/blob/b5c9cf037cbce672101725f269470135b9b2c5c4/src/sage/cpython/atexit.pyx -- nosy: +chrahunt ___ Python tracker

[issue32082] atexit module: allow getting/setting list of handlers directly

New submission from Erik Bray : In Python 2 it was possible to directly manipulate the list of registered atexit handlers through atexit._exithandlers. Obviously I'm not complaining that this went away, as it was an underscored attribute. But this possibility was still useful in the context