[Python-Dev] backported Enum

Eli Bendersky eliben at gmail.com
Sun Jun 16 22:13:00 CEST 2013

On Sun, Jun 16, 2013 at 8:19 AM, Barry Warsaw <barry at python.org> wrote:

> On Jun 15, 2013, at 11:53 PM, Ethan Furman wrote:
> >Note that while flufl.enum was the inspiration, it is not the version that
> >went into 3.4.
> I haven't yet decided whether to continue with development of flufl.enum or
> not.  I think there's a lot of value in promoting a standard enum library
> and
> having PEP 435 in both the 3.4 stdlib and in a good backport may outweigh
> the
> differences.  I mostly agree with everything in PEP 435 <wink>.
> One big test will be porting Mailman 3 to enum34.  I expect that to mostly
> Just Work and I don't think the differences will affect it (I've already
> adjusted for the lack of inheritance - mostly I have to see what effect it
> will have on the database layer).
> OTOH, if folks really depend on the differences in flufl.enum, I will
> probably
> at least continue to maintain it, but not add any new features.

If you write down the process of porting mailmain from flufl to stdlib.enum
in some place, it can make the process much easier for others, and even
encourage them to follow the same path.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20130616/ea001ee9/attachment.html>

More information about the Python-Dev mailing list