STINNER Victor <vstin...@python.org> added the comment:
> Drawback: it is a backward incompatible change. Code which worked by luck > previously no longer works. I'm talking about applications which rely on > __del__() methods being calling in an exact order and expect Python being in > a specific state. Python does not provide any warranty in which order finalizers are called: https://docs.python.org/dev/reference/datamodel.html#object.__del__ PyPy is a good concrete example of finalizers being called in a different order. An application must not rely on the finalizer order, but manage resources explicitly by calling close() methods or using context managers. Python emits ResourceWarning on this purpose. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue42671> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
