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 barry, eli.bendersky, ethan.furman
Date 2016-05-08.23:45:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1462751121.21.0.925705458571.issue26981@psf.upfronthosting.co.za>
In-reply-to
Content
_sunder_ methods are reserved for internal Enum use, and if the user tries to use any an exception is raised.

Consequently, the enum34 backport uses __order__ instead of _order_ to specify a definition order for its members.

I would like to do two things:

1) add _order_ to the stdlib version

2) ensure the actual definition order is the same as what is specified
   in _order_
History
Date User Action Args
2016-05-08 23:45:21ethan.furmansetrecipients: + ethan.furman, barry, eli.bendersky
2016-05-08 23:45:21ethan.furmansetmessageid: <1462751121.21.0.925705458571.issue26981@psf.upfronthosting.co.za>
2016-05-08 23:45:21ethan.furmanlinkissue26981 messages
2016-05-08 23:45:20ethan.furmancreate