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 ncoghlan
Recipients barry, ethan.furman, ncoghlan
Date 2013-05-13.04:09:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CADiSq7cXX5RvnXpKC0JrD+etpGj_mncnuCJM7ZKts2vVACte6g@mail.gmail.com>
In-reply-to <51904A8A.3080604@stoneleaf.us>
Content
Accepting awkward implementation details when their rationale no longer
applies doesn't make sense to me, no.

The functional API originally used integers for good reasons. Over the
course of the enum discussions, those reasons evaporated, but this wasn't
noticed until after the PEP was accepted.

However, the acceptance of the PEP is why I have proposed this as a
post-incorporation change.
History
Date User Action Args
2013-05-13 04:09:05ncoghlansetrecipients: + ncoghlan, barry, ethan.furman
2013-05-13 04:09:05ncoghlanlinkissue17961 messages
2013-05-13 04:09:04ncoghlancreate