➜

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 gregory.p.smith
Recipients ethan.furman, gregory.p.smith, novas0x2a, python-dev, r.david.murray, serhiy.storchaka
Date 2015-12-22.21:23:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1450819438.99.0.272381281331.issue24840@psf.upfronthosting.co.za>
In-reply-to
Content 
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
History
Date User Action Args
2015-12-22 21:23:59gregory.p.smithsetrecipients: + gregory.p.smith, r.david.murray, ethan.furman, python-dev, serhiy.storchaka, novas0x2a
2015-12-22 21:23:58gregory.p.smithsetmessageid: <1450819438.99.0.272381281331.issue24840@psf.upfronthosting.co.za>
2015-12-22 21:23:58gregory.p.smithlinkissue24840 messages
2015-12-22 21:23:58gregory.p.smithcreate