[Armin] > I claim that there is nothing unreliable or depending on import order > here, as > long as all concerned parties do the right thing. Right. It's only unreliable if a party takes an obvious, but not wise approach. > Now if there are other > good > reasons to deprecate sys.exitfunc, like it being another way of doing > something for which a better interface is provided, then fine. That is the case. The API for at exit accepts function arguments and automatically handles multiple exit functions. It is careful to handle the multiple exits using pop() in case another exit function alters the function list or in case multiple threads are using atexit. So, yes there is a better API that should be the one preferred way to do it. Raymond
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