> On May 21, 2015, at 9:50 PM, Scott Kitterman <deb...@kitterman.com> wrote: > > On Friday, May 22, 2015 12:34:02 AM Brian May wrote: >> On Fri, 22 May 2015 at 07:14 Scott Kitterman <deb...@kitterman.com> wrote: >>> I was considering the idea of porting things from ipaddr to ipaddress for >>> python2, but there's a lot more of that then there is for ipaddress (which >>> is >>> up to only two packages we know about). >> >> As it is a goal to have everything Python3 compliant, and as Jessie no >> longer has python3-ipaddr (it was in wheezy), everything is going to have >> to support ipaddress for python3 anyway. >> >> I don't see why we don't drop python-ipaddr, and replace it with >> python-ipaddress. > > I dropped python3-ipaddr once python3.3 was default since it comes with > ipaddress. For python3, everthing should use ipaddress. > > At some point it might make sense to switch. There's about 20 packages in the > archive that use python-ipaddr versus none with one or two candidates using > python-ipaddress in python2. Porting two is easier than porting 20. > > I'm also concerned that because of type processing differences (strings versus > bytes and UTF-8 by default versus not) there is potential for subtle > incompatibilities in the backported ipaddress. I had complaints on an > upstream project that uses ipaddress with python3 when it was available > failing with ipaddress in python2. > > Scott K > > > -- > To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: https://lists.debian.org/2512839.pZrC1BOzKj@kitterma-e6430 >
I released pip 7 last night, as part of that I looked at switching from ipaddress to ipaddr as a favor to Barry to try and help him get the new pip into Debian. I've never used the ipaddr library before so I was flying blind with it. I'm not sure if I was looking at the wrong ipaddr or something but the documentation I found was pretty crappy and looking at it I didn't see how to actually use ipaddr the same way I was using ipaddress in pip. In addition to that, the API doesn't really look the same as the ipaddress to me so it's going to require some sort of compatability shim maintained in pip in order to be able to run one module on Python 2 and another module on Python 3. Given all of that and the fact I didn't feel like spending a bunch of time going down a rathole to switch dependencies when we already had a perfectly reasonable dependency that handled it I went ahead and just released pip 7 with the ipaddress dependency still. I'm not entirely sure why that's an unreasonable dependency here, it has a different name than ipaddr does, at least in the PyPI modules, so it should be entirely possible to have them both installed side by side without any conflicts. --- Donald Stufft PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
