On Friday, May 22, 2015 02:17:59 PM Ian Cordasco wrote: > On Fri, May 22, 2015 at 10:12 AM, Tristan Seligmann > > <mithra...@mithrandi.net> wrote: > > On 22 May 2015 at 16:06, Tristan Seligmann <mithra...@mithrandi.net> wrote: > >> Or are you saying that the ipaddress backport is not compatible with > >> python3 stdlib's ipaddress? (This would be a very unfortunate state of > >> affairs, but impossible to imagine) > > > > This should have been "*not* impossible", of course. > > Based purely on the fact that the current version of ipaddr is > undocumented, I would strongly be against any patch to packaged > software that causes a dependency on it for the sole purpose of > Debian's packaging of that software. You're asking the maintainers of > those packages to maintain patches for things that are undocumented. > In my opinion, Scott, if your'e so adamant about not packaging > ipaddress for Python 2, you should work with ipaddr to fix things so > maintainers can reliably maintain the software. Until that is fixed, I > think Tristan's packaging should move forward so Debian doesn't fall > too far behind pip.
I don't know what happens on pip. I know if I do: >>> import ipaddr >>> help(ipaddr) The module documentation is all there exactly like it should be. I should have a patch today. You'll certainly have a patch from me faster than python-ipaddress will get through New. 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/3841486.q05gmfchXz@kitterma-e6430
