[issue21512] time module becomes None after raise SystemExit

Changes by Antoine Pitrou : -- resolution: not a bug -> wont fix status: open -> closed ___ Python tracker ___ ___ Python-bugs-list ma

[issue21512] time module becomes None after raise SystemExit

Antoine Pitrou added the comment: Well, let's call it a limitation rather than a bug. When creating a global variable (such as "a" in your example), that variable is kept alive at least as long as the module containing it. However, modules usually live until very late in the interpreter shutdow

[issue21512] time module becomes None after raise SystemExit

Changes by Ezio Melotti : -- nosy: +benjamin.peterson, pitrou resolution: -> not a bug status: open -> pending ___ Python tracker ___ ___

[issue21512] time module becomes None after raise SystemExit

New submission from Ryder Lewis: I'm not sure if this is a bug or expected behavior, but basically what I want to do is log the timestamp when an application exits. Sample script to illustrate the issue: try.py import time class A(): def __init__(self): print("Initializi