[Python-Dev] backported Enum (original) (raw)

Gregory P. Smith greg at krypto.org
Sun Jun 16 00:43:10 CEST 2013

I tend to just pick a name and stick with it. subprocess32 is subprocess backported from 3.2 (with the 3.3 timeout feature also in it). unittest2 is unittest from 2.7.

It tends to work. and it also emphasizes that i'm unlikely to backport future non-bugfix updates beyond the release mentioned and merely focus on keeping it stable and available for use on older pythons.

A "backport" namespace is a neat idea but unless someone's going to create a system for backports to register which versions they are backports from and automagically have sub-module imports from backport pick the backported code or the standard library version when the Python VM is recent enough to not need a backport I wouldn't bother claiming that name. (and even that feels like overengineering)

-gps

On Sat, Jun 15, 2013 at 12:46 PM, Ethan Furman <ethan at stoneleaf.us> wrote:

So I have the stdlb 3.4 Enum backported for both earlier 3.x and back to 2.4 in the 2.x series.

I would like to put this on PyPI, but the enum name is already taken. Would it be inappropriate to call it stdlib.enum? -- Ethan _______** Python-Dev mailing list Python-Dev at python.org http://mail.python.org/**mailman/listinfo/python-dev<http://mail.python.org/mailman/listinfo/python-dev> Unsubscribe: http://mail.python.org/mailman/options/python-dev/ greg%40krypto.org<http://mail.python.org/mailman/options/python-dev/greg%40krypto.org> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20130615/805c09a8/attachment.html>

More information about the Python-Dev mailing list