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 John Belmonte, Manjusaka, ethan.furman, hauntsaninja, hroncok, jbelmonte, pablogsal, veky
Date 2021-05-27.20:16:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1622146578.13.0.166879219264.issue44242@roundup.psfhosted.org>
In-reply-to
Content
I'm very much of the practicality beats purity philosophy, so I want to support the OP's flag without making them jump through hoops.

On the flip side, I also appreciate that there are folks that want the extra security...

So here's my plan:  remove the creation time check (which will remove the error for the OP), and then add a decorator to the enum module that does that creation time check -- just like the `unique` decorator enforces no aliases.

Now I just need a good name for that decorator:

- complete ?
- exhaustive ?
- all_named ?
- check_for_unnamed ?
History
Date User Action Args
2021-05-27 20:16:18ethan.furmansetrecipients: + ethan.furman, jbelmonte, veky, hroncok, pablogsal, Manjusaka, John Belmonte, hauntsaninja
2021-05-27 20:16:18ethan.furmansetmessageid: <1622146578.13.0.166879219264.issue44242@roundup.psfhosted.org>
2021-05-27 20:16:18ethan.furmanlinkissue44242 messages
2021-05-27 20:16:17ethan.furmancreate