[Python-Dev] Minor change to Enum -- should it go into 3.5.2? (original) (raw)
Ethan Furman ethan at stoneleaf.us
Sun May 8 16:10:05 EDT 2016
- Previous message (by thread): [Python-Dev] Tracker Etiquette
- Next message (by thread): [Python-Dev] Minor change to Enum -- should it go into 3.5.2?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Currently, the Enum creation process ignores dunder attributes, and blocks all sunder attributes.
Because of this, the enum34 backport used order instead of order to provide a mechanism for ordering the enum members (which I never really liked).
However, I've been working on my aenum [1] package, which uses several other sunder attributes (for python2 compatibility) so I enabled order instead and promote that spelling in the docs.
Unlike the other sunder attributes, order has no meaningful affect in Python 3 so I'd like to change the stdlib Enum to allow it (and either ignore completely, or check it is the same as the definition order).
My question is: Should I put this change in 3.5.2?
Yes means 3.5.2+ will work with order, 3.4, 3.5.0, and 3.5.1 will not;
No means 3.4 and all of 3.5 will not.
--
Ethan
[1] https://pypi.python.org/pypi/aenum
- Previous message (by thread): [Python-Dev] Tracker Etiquette
- Next message (by thread): [Python-Dev] Minor change to Enum -- should it go into 3.5.2?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]