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 ethan.furman
Recipients Tom.Brown, ethan.furman
Date 2021-06-10.21:55:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1623362143.73.0.896526487542.issue44342@roundup.psfhosted.org>
In-reply-to
Content
Looking into this I think the root of the problem is the way `reduce` is handled -- currently, Enum's `__reduce_ex__` works by returning the class, and the value to use to lookup the member.  Because that lookup can fail with complex enums, EnumType will sabotage `reduce` if it can't find support in the new enum class.

However, if `__reduce_ex__` working by returning

    `getattr, (self.__class, self._name_)`

then we should be fine, as that should never fail.
History
Date User Action Args
2021-06-10 21:55:43ethan.furmansetrecipients: + ethan.furman, Tom.Brown
2021-06-10 21:55:43ethan.furmansetmessageid: <1623362143.73.0.896526487542.issue44342@roundup.psfhosted.org>
2021-06-10 21:55:43ethan.furmanlinkissue44342 messages
2021-06-10 21:55:43ethan.furmancreate