[issue16178] atexit._run_exitfuncs should be a public API

2014-07-13 Thread Raymond Hettinger
Raymond Hettinger added the comment: Closed due to lack on interest. -- nosy: +rhettinger resolution: -> out of date status: open -> closed ___ Python tracker ___ __

[issue16178] atexit._run_exitfuncs should be a public API

2014-07-13 Thread Gregory P. Smith
Gregory P. Smith added the comment: I don't currently have a need for this so, no. -- ___ Python tracker ___ ___ Python-bugs-list mail

[issue16178] atexit._run_exitfuncs should be a public API

2014-07-13 Thread Mark Lawrence
Mark Lawrence added the comment: @Gregory do you intend to follow up on this? -- nosy: +BreamoreBoy versions: +Python 3.5 -Python 3.4 ___ Python tracker ___ _

[issue16178] atexit._run_exitfuncs should be a public API

2012-10-11 Thread Philip Mountifield
Changes by Philip Mountifield : -- nosy: +Philip.Mountifield ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue16178] atexit._run_exitfuncs should be a public API

2012-10-09 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- nosy: +sbt ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue16178] atexit._run_exitfuncs should be a public API

2012-10-09 Thread Gregory P. Smith
New submission from Gregory P. Smith: The atexit module's _run_exitfuncs() function needs to be a public API. In Python 2.x it was exposed through a disgusting hack as "sys.exitfunc()" that the atexit module monkeypatched into place at import time. This monkeypatching was cleaned up in Python