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 eli.bendersky
Recipients barry, eli.bendersky, ethan.furman, ncoghlan, pitrou
Date 2013-06-19.13:00:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> The fact "str(x)" returns the fully qualified name for IntEnum worries me a bit, but if there's a real backwards compatibility problem there (rather than a theoretical one), hopefully we'll see it once we start converting socket and errno.

What is the theoretical problem here? I though that it's an explicit design goal of enums? Which RED - Color.RED, or MeatReadiness.RED? For sockets:

>>> class SocketType(IntEnum):
...   SOCK_STREAM = 1
...   SOCK_DGRAM = 2
>>> str(SocketType.SOCK_STREAM)

Looks pretty good to me in terms of debuggability.
Date User Action Args
2013-06-19 13:00:52eli.benderskysetrecipients: + eli.bendersky, barry, ncoghlan, pitrou, ethan.furman
2013-06-19 13:00:52eli.benderskysetmessageid: <>
2013-06-19 13:00:52eli.benderskylinkissue17961 messages
2013-06-19 13:00:51eli.benderskycreate