Gregory P. Smith added the comment: This change breaks existing code that is relying on the behavior of the enum API as shipped in 3.4 and 3.5. Please do NOT do this.
Worse, you've landed this change in a "stable" release of the enum34 "backport" module (1.1.1) despite it never having been released as a stable Python API. Please do not let *the backport* get ahead of the latest stable released Python API. https://bitbucket.org/stoneleaf/enum34/issues/10/versions-of-enum34-111-break-support-for ---------- nosy: +gregory.p.smith resolution: fixed -> status: closed -> open versions: +Python 3.6 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue24840> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
