[issue42248] Raised exception in Enum keeping user objects alive unnecessarily

Change by Ethan Furman : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue42248] Raised exception in Enum keeping user objects alive unnecessarily

Ethan Furman added the comment: Going back through the various bug fixes that got cut from 3.10 to re-add to 3.10.1. -- ___ Python tracker ___

[issue42248] Raised exception in Enum keeping user objects alive unnecessarily

Antoine Pitrou added the comment: It seems the problem is that bpo-44559 reset the enum module to a previous state without the bugfix. -- ___ Python tracker ___

[issue42248] Raised exception in Enum keeping user objects alive unnecessarily

Antoine Pitrou added the comment: Indeed, changeset 8c14f5a787b21d5a1eae5d5ee981431d1c0e055f is part of git main, but is not on the 3.10 branch AFAICT. -- ___ Python tracker

[issue42248] Raised exception in Enum keeping user objects alive unnecessarily

Antoine Pitrou added the comment: It appears this is *not* fixed in 3.10.0: Python 3.10.0 (default, Oct 13 2021, 08:45:17) [GCC 10.2.1 20210110] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import signal, gc >>> class App: pass ... >>> def create_app():

[issue42248] Raised exception in Enum keeping user objects alive unnecessarily

Mark Dickinson added the comment: Thank you for the quick fix! -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue42248] Raised exception in Enum keeping user objects alive unnecessarily

Change by Ethan Furman : -- assignee: -> ethan.furman resolution: -> fixed stage: patch review -> resolved status: open -> closed type: enhancement -> behavior versions: +Python 3.10, Python 3.9 ___ Python tracker

[issue42248] Raised exception in Enum keeping user objects alive unnecessarily

Ethan Furman added the comment: New changeset 6379924ecd51e346b42b0293da0f4442a0f67707 by Ethan Furman in branch '3.9': [3.9] bpo-42248: [Enum] ensure exceptions raised in ``_missing_`` are released (GH-25350). (GH-25370)

[issue42248] Raised exception in Enum keeping user objects alive unnecessarily

Ethan Furman added the comment: New changeset f396a1a940f8608a4be2a9ac4ef82e37c198ecd3 by Ethan Furman in branch '3.8': [3.8] bpo-42248: [Enum] ensure exceptions raised in ``_missing_`` are released (GH-25350). (GH-25369)

[issue42248] Raised exception in Enum keeping user objects alive unnecessarily

Change by Ethan Furman : -- pull_requests: +24103 pull_request: https://github.com/python/cpython/pull/25370 ___ Python tracker ___

[issue42248] Raised exception in Enum keeping user objects alive unnecessarily

Change by Ethan Furman : -- pull_requests: +24102 pull_request: https://github.com/python/cpython/pull/25369 ___ Python tracker ___

[issue42248] Raised exception in Enum keeping user objects alive unnecessarily

Ethan Furman added the comment: New changeset 8c14f5a787b21d5a1eae5d5ee981431d1c0e055f by Ethan Furman in branch 'master': bpo-42248: [Enum] ensure exceptions raised in ``_missing_`` are released (GH-25350) https://github.com/python/cpython/commit/8c14f5a787b21d5a1eae5d5ee981431d1c0e055f

[issue42248] Raised exception in Enum keeping user objects alive unnecessarily

Change by Ethan Furman : -- keywords: +patch pull_requests: +24085 stage: -> patch review pull_request: https://github.com/python/cpython/pull/25350 ___ Python tracker ___

[issue42248] Raised exception in Enum keeping user objects alive unnecessarily

Mark Dickinson added the comment: Here's a cut-down example, at the prompt: Python 3.9.2 (default, Mar 31 2021, 05:47:22) [Clang 11.0.3 (clang-1103.0.32.62)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import signal >>> class App: pass ... >>> def

[issue42248] Raised exception in Enum keeping user objects alive unnecessarily

Mark Dickinson added the comment: I'm running into this, too, on Python 3.9.2; in my case it's causing segmentation faults in a wxPython-based application. Those segfaults aren't the fault of the reference cycle, of course; they're a result of wxPython being finicky about object cleanup

[issue42248] Raised exception in Enum keeping user objects alive unnecessarily

Gerald Dalley added the comment: I and a few others have run into issues with the Enum constructors producing spurious reference cycles. This can cause memory explosions if large objects like numpy arrays are held in any of the relevant stack frames. Based on

[issue42248] Raised exception in Enum keeping user objects alive unnecessarily

New submission from Eric Froemling : I've run into an issue where exceptions thrown by Enum constructors are keeping my objects alive. The underlying issue seems to be the same as https://bugs.python.org/issue36820 The same method used to fix the issue above seems to work here: simply adding