From cia at mud.ro  Fri Aug 23 12:35:19 2013
From: cia at mud.ro (adrian ilarion Ciobanu)
Date: Fri, 23 Aug 2013 13:35:19 +0300
Subject: [Python-porting] 3to2 ipaddress.py backport
Message-ID: <CAMOmXsCJcOgG7RdA=3J2Lpfypijrw7QHUMq+QRteN0Q2vzDuFA@mail.gmail.com>

Hello list,

I backported a while ago the ipaddress module (being a pretty useful piece
of code), given that in my case most of the systems needing it were running
python 2.x (still true).

Do any of you see any (good) reasons for this module to be proposed for
inclusion in 2.x? (given some code cleanup / rewrite and unittests included
and making the assumption that 3to2 feature backport is acceptable).

tip: the current patch looks compatible with both 3 and 2, although not
fully tested. with a little bit of more work (full code coverage tests at
least) there shouldn't be any need of maintaining different versions for 2
and 3.

diff: https://gist.github.com/malfaux/6317110
code: https://github.com/malfaux/backport32/blob/master/ipaddress.py


thank you,

adrian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-porting/attachments/20130823/51a747af/attachment.html>

From brett at python.org  Mon Aug 26 14:04:09 2013
From: brett at python.org (Brett Cannon)
Date: Mon, 26 Aug 2013 08:04:09 -0400
Subject: [Python-porting] 3to2 ipaddress.py backport
In-Reply-To: <CAMOmXsCJcOgG7RdA=3J2Lpfypijrw7QHUMq+QRteN0Q2vzDuFA@mail.gmail.com>
References: <CAMOmXsCJcOgG7RdA=3J2Lpfypijrw7QHUMq+QRteN0Q2vzDuFA@mail.gmail.com>
Message-ID: <CAP1=2W5SKZuu0o+pbLUzLkXoAS1bb5u6OV8NzONg6f4G1+ZS=g@mail.gmail.com>

Because Python 2.7 is the last version in the 2.x series and has already
been released it means no additions to the stdlib can be made. If it were
allowed it would mean some software could run on 2.7.6 but not on 2.7.5
because they just happened not to have upgraded to the version when the
module was added.

What you could consider doing, though, is posting it on PyPI.


On Fri, Aug 23, 2013 at 6:35 AM, adrian ilarion Ciobanu <cia at mud.ro> wrote:

> Hello list,
>
> I backported a while ago the ipaddress module (being a pretty useful piece
> of code), given that in my case most of the systems needing it were running
> python 2.x (still true).
>
> Do any of you see any (good) reasons for this module to be proposed for
> inclusion in 2.x? (given some code cleanup / rewrite and unittests included
> and making the assumption that 3to2 feature backport is acceptable).
>
> tip: the current patch looks compatible with both 3 and 2, although not
> fully tested. with a little bit of more work (full code coverage tests at
> least) there shouldn't be any need of maintaining different versions for 2
> and 3.
>
> diff: https://gist.github.com/malfaux/6317110
> code: https://github.com/malfaux/backport32/blob/master/ipaddress.py
>
>
> thank you,
>
> adrian
>
>
> _______________________________________________
> Python-porting mailing list
> Python-porting at python.org
> http://mail.python.org/mailman/listinfo/python-porting
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-porting/attachments/20130826/5e81498b/attachment.html>