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