[issue39451] enum.Enum reference count leaks

Ethan Furman added the comment: Thanks, Dan, for checking this out. As you noted, a garbage collection solved the issue, so I'm not going to worry about it. -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker

[issue39451] enum.Enum reference count leaks

Change by hongweipeng : -- nosy: +hongweipeng ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue39451] enum.Enum reference count leaks

Dan Gass added the comment: Sorry for not thinking of trying this sooner. Running garbage collection, import gc; gc.collect(), releases the resources and restores the expected reference counts. >From my perspective, this is satisfactory and could justify closing this bug >report. The exce

[issue39451] enum.Enum reference count leaks

Change by Raymond Hettinger : -- assignee: -> ethan.furman priority: normal -> low ___ Python tracker ___ ___ Python-bugs-list mail

[issue39451] enum.Enum reference count leaks

Change by Karthikeyan Singaravelan : -- nosy: +barry, eli.bendersky, ethan.furman ___ Python tracker ___ ___ Python-bugs-list mailin

[issue39451] enum.Enum reference count leaks

New submission from Dan Gass : Given (1) instantiation of an enumeration class with an invalid value (2) a try/except around the instantiation where the exception is ignored Then: An unneeded reference to the bad value is lost (as well as other values that I suspect are local variables within