A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2004-August/047916.html below:

[Python-Dev] Deprecate sys.exitfunc?

[Python-Dev] Deprecate sys.exitfunc? [Python-Dev] Deprecate sys.exitfunc?Guido van Rossum guido at python.org
Tue Aug 17 03:21:55 CEST 2004
> Multiple well-written modules can use sys.exitfunc in a way that is
> compatible.  atexit is merely a glue to discourage non-well-written
> modules.  I'd say that atexit should be encouraged but there is
> nothing wrong with using sys.exitfunc directly, if one is aware of
> the common patching pattern: "save-old-value,
> replace-with-my-function, upon-call-invoke-saved-old-value".

But why offer two ways of doing the same thing?  Apart from b/w
compatibility, what's the advantage of using sys.exitfunc directly?

--Guido van Rossum (home page: http://www.python.org/~guido/)
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4