This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author dan.gass@gmail.com
Recipients barry, dan.gass@gmail.com, eli.bendersky, ethan.furman
Date 2020-01-26.17:26:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1580059593.27.0.745364531182.issue39451@roundup.psfhosted.org>
In-reply-to
Content
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 exception logic in Enum.__new__ could potentially be cleaned up for this use case, just not sure if that would introduce risk for other use cases. 

I am guessing (from the perspective of the larger Python exception handling design and implementation) what this bug report demonstrates had been previously thought through.
History
Date User Action Args
2020-01-26 17:26:33dan.gass@gmail.comsetrecipients: + dan.gass@gmail.com, barry, eli.bendersky, ethan.furman
2020-01-26 17:26:33dan.gass@gmail.comsetmessageid: <1580059593.27.0.745364531182.issue39451@roundup.psfhosted.org>
2020-01-26 17:26:33dan.gass@gmail.comlinkissue39451 messages
2020-01-26 17:26:33dan.gass@gmail.comcreate