[issue17186] no way to introspect registered atexit handlers

Change by Irit Katriel : -- components: +Library (Lib) type: -> enhancement versions: +Python 3.11 -Python 3.4 ___ Python tracker ___ _

[issue17186] no way to introspect registered atexit handlers

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

[issue17186] no way to introspect registered atexit handlers

Barry A. Warsaw added the comment: On Feb 22, 2013, at 06:54 PM, Charles-François Natali wrote: >Charles-François Natali added the comment: > >> Barry advised me to open this issue as it's a functional regression from >> Python 2. > >But it was relying on a private and non documented feature in

[issue17186] no way to introspect registered atexit handlers

Antoine Pitrou added the comment: I don't think you want your test suite to run your atexit handlers at exit, so you should probably mock atexit.register instead. -- nosy: +pitrou ___ Python tracker __

[issue17186] no way to introspect registered atexit handlers

Chris Withers added the comment: I can think of other use cases. Anyway, I'm just glad your opinion isn't the only one there is ;-) -- ___ Python tracker ___ ___

[issue17186] no way to introspect registered atexit handlers

Charles-François Natali added the comment: > Barry advised me to open this issue as it's a functional regression from > Python 2. But it was relying on a private and non documented feature in Python 2, so it's not really a regression. > My use case is unit testing code that registers atexit ha

[issue17186] no way to introspect registered atexit handlers

Charles-François Natali added the comment: Could you please give an example of why this would be a useful addition? I can see the usage of removing a handler, but the user should know which handlers are registered. -- nosy: +neologix ___ Python track

[issue17186] no way to introspect registered atexit handlers

Chris Withers added the comment: Barry advised me to open this issue as it's a functional regression from Python 2. My use case is unit testing code that registers atexit handlers and making sure the right handlers are registered with the correct parameters. -- __

[issue17186] no way to introspect registered atexit handlers

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue17186] no way to introspect registered atexit handlers

New submission from Chris Withers: Python 2 had a private but usable way of introspecting and manipulating registered atexit handlers by way of the atexit._exithandlers. In Python 3, registering and unregistering are handled, but there is no longer a way to see what atexit handlers are registe