On Jun 22, 2013, at 07:28 PM, Julian Taylor wrote: >are the enums already stable enough for backports? >3.4 is still quite a while away. I think so, yes. The PEP 435 has been accepted and the code is in 3.4's Mercurial tree[1]. I have a branch adaptings Mailman 3 from using flufl.enum to enum34; it took about an hour, and was mostly mechanical[2]. There's an open bug about trying to make IntEnums more compatible with the default JSON support, but I think that's a separate issue and probably won't affect enum. I think these are worth promoting as the preferred way of doing enums in Python. Cheers, -Barry [1] http://docs.python.org/3.4/library/enum.html [2] http://mail.python.org/pipermail/python-dev/2013-June/126938.html [3] http://bugs.python.org/issue18264
Attachment:
signature.asc
Description: PGP signature