Message191464
| 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 |
<1371646852.02.0.678955487556.issue17961@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> 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)
'SocketType.SOCK_STREAM'
Looks pretty good to me in terms of debuggability. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2013年06月19日 13:00:52 | eli.bendersky | set | recipients:
+ eli.bendersky, barry, ncoghlan, pitrou, ethan.furman |
| 2013年06月19日 13:00:52 | eli.bendersky | set | messageid: <1371646852.02.0.678955487556.issue17961@psf.upfronthosting.co.za> |
| 2013年06月19日 13:00:52 | eli.bendersky | link | issue17961 messages |
| 2013年06月19日 13:00:51 | eli.bendersky | create |
|