[issue26981] add compatibility shim for enum34 backport

Ethan Furman added the comment: Thanks! -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue26981] add compatibility shim for enum34 backport

Roundup Robot added the comment: New changeset bdfd4c8384de by Ethan Furman in branch 'default': issue26981: fix typo https://hg.python.org/cpython/rev/bdfd4c8384de -- ___ Python tracker

[issue26981] add compatibility shim for enum34 backport

SilentGhost added the comment: Ethan, in Misc/NEWS it says "compatibility ship" -- nosy: +SilentGhost ___ Python tracker ___

[issue26981] add compatibility shim for enum34 backport

Changes by Ethan Furman : -- resolution: -> fixed stage: needs patch -> resolved status: open -> closed ___ Python tracker ___

[issue26981] add compatibility shim for enum34 backport

Roundup Robot added the comment: New changeset 10830e1b2966 by Ethan Furman in branch 'default': issue26981: add _order_ compatibility shim to enum.Enum https://hg.python.org/cpython/rev/10830e1b2966 -- nosy: +python-dev ___ Python tracker

[issue26981] add compatibility shim for enum34 backport

Ethan Furman added the comment: Issue 26988 reverted. Need to add shim here. -- resolution: fixed -> status: closed -> open ___ Python tracker ___

[issue26981] add compatibility shim for enum34 backport

Ethan Furman added the comment: Done in issue26988. -- resolution: -> fixed status: open -> closed superseder: -> Add AutoNumberedEnum to stdlib ___ Python tracker

[issue26981] add compatibility shim for enum34 backport

Ethan Furman added the comment: It would, but that's not what we did. Currently we have _name_ and _value_; the backport uses __order__ because I didn't want the stdlib version having a hairball when someone tried to use a 2.7 Enum in 3.4 and it didn't occur to me at the time to just add and

[issue26981] add compatibility shim for enum34 backport

Eric V. Smith added the comment: Doesn't namedtuple use _fields (as opposed to _fields_) for a similar purpose? Would Enum using _order be more consistent with that? -- nosy: +eric.smith ___ Python tracker

[issue26981] add compatibility shim for enum34 backport

New submission from Ethan Furman: _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: