On Mon, 8 Jun 2015 at 15:27 Tristan Seligmann
wrote:
> >>> import ipaddr, ipaddress
> >>> ipaddress.ip_address(b'\x7f\x00\x00\x01')
> IPv4Address(u'127.0.0.1')
> >>> ipaddr.IPAddress(b'\x7f\x00\x00\x01')
> Traceback (most recent call last):
> File "", line 1, in
> File
> "/home/mithrandi/dep
Control: tag -1 - wontfix
On Fri, 22 May 2015 at 17:06 Scott Kitterman wrote:
> There are far more users of ipaddr than ipaddress. There's exactly two
> API differences. I'm willing to look at pip and propose a patch to work
> with either.
>
I've discovered yet another API incompatibility whi
On Saturday, May 23, 2015 02:27:45 PM Scott Kitterman wrote:
> On May 23, 2015 12:42:35 PM EDT, Scott Kitterman
wrote:
> >On Friday, May 22, 2015 02:17:59 PM Ian Cordasco wrote:
> >> On Fri, May 22, 2015 at 10:12 AM, Tristan Seligmann
> >>
> >> wrote:
> >> > On 22 May 2015 at 16:06, Tristan Sel
On May 23, 2015 12:42:35 PM EDT, Scott Kitterman wrote:
>On Friday, May 22, 2015 02:17:59 PM Ian Cordasco wrote:
>> On Fri, May 22, 2015 at 10:12 AM, Tristan Seligmann
>>
>> wrote:
>> > On 22 May 2015 at 16:06, Tristan Seligmann
>
>wrote:
>> >> Or are you saying that the ipaddress backport is n
On Friday, May 22, 2015 02:17:59 PM Ian Cordasco wrote:
> On Fri, May 22, 2015 at 10:12 AM, Tristan Seligmann
>
> wrote:
> > On 22 May 2015 at 16:06, Tristan Seligmann
wrote:
> >> Or are you saying that the ipaddress backport is not compatible with
> >> python3 stdlib's ipaddress? (This would b
On Friday, May 22, 2015 02:17:59 PM Ian Cordasco wrote:
> On Fri, May 22, 2015 at 10:12 AM, Tristan Seligmann
>
> wrote:
> > On 22 May 2015 at 16:06, Tristan Seligmann
wrote:
> >> Or are you saying that the ipaddress backport is not compatible with
> >> python3 stdlib's ipaddress? (This would b
On Fri, May 22, 2015 at 10:12 AM, Tristan Seligmann
wrote:
> On 22 May 2015 at 16:06, Tristan Seligmann 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)
>
On 22 May 2015 at 16:06, Tristan Seligmann 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.
--
mithrand
On May 22, 2015 10:06:34 AM EDT, Tristan Seligmann
wrote:
>On 22 May 2015 at 15:43, Donald Stufft wrote:
>> 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 wa
On 22 May 2015 at 15:43, Donald Stufft wrote:
> 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 doe
> On May 21, 2015, at 9:50 PM, Scott Kitterman wrote:
>
> On Friday, May 22, 2015 12:34:02 AM Brian May wrote:
>> On Fri, 22 May 2015 at 07:14 Scott Kitterman wrote:
>>> I was considering the idea of porting things from ipaddr to ipaddress for
>>> python2, but there's a lot more of that then th
On Friday, May 22, 2015 12:34:02 AM Brian May wrote:
> On Fri, 22 May 2015 at 07:14 Scott Kitterman 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
On Fri, 22 May 2015 at 07:14 Scott Kitterman 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
On Thursday, May 21, 2015 04:07:24 PM Barry Warsaw wrote:
> On May 21, 2015, at 03:44 PM, Scott Kitterman wrote:
> >>ipaddress is apparently also a new dependency of pip.
> >
> >For python2?
>
> Yes, sorry, just for Python 2.
>
> -Barry
So far for python-ipaddress (for python 2), that's two pack
On May 21, 2015, at 03:44 PM, Scott Kitterman wrote:
>>ipaddress is apparently also a new dependency of pip.
>
>For python2?
Yes, sorry, just for Python 2.
-Barry
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@li
t;>
>>> * Package name: python-ipaddress
>>> Version : 1.0.7
>>> Upstream Author : Philipp Hagemeister
>>> * URL : https://github.com/phihag/ipaddress
>>> * License : PSF
>>> Programming Lang: Python
>>
: 1.0.7
>> Upstream Author : Philipp Hagemeister
>> * URL : https://github.com/phihag/ipaddress
>> * License : PSF
>> Programming Lang: Python
>> Description : Backport of the ipaddress module from Python 3.3
>>
>> This is a new depen
Control: tag -1 + wontfix
On 14 May 2015 at 13:45, Scott Kitterman wrote:
> Is this 100% compatible with ipaddress from upstream now? The problem I ran
> into before is that when importing ipaddress and it turned out to be this one
> and not the upstream one, the API was different, so it didn't
On Thursday, May 14, 2015 06:55:40 AM Tristan Seligmann wrote:
> On 14 May 2015 at 06:04, Scott Kitterman wrote:
> > Why can't python-cryptography use python-ipaddr that's already in the
> > archive?
> cryptography is python2/3 dual-source. Carrying a Debian-specific
> patch[1] that introduces a s
On 14 May 2015 at 06:04, Scott Kitterman wrote:
> Why can't python-cryptography use python-ipaddr that's already in the archive?
cryptography is python2/3 dual-source. Carrying a Debian-specific
patch[1] that introduces a slew of fallback imports to ipaddr, solely
to avoid uploading a new package
hub.com/phihag/ipaddress
> * License : PSF
> Programming Lang: Python
> Description : Backport of the ipaddress module from Python 3.3
>
> This is a new dependency of python-cryptography. I intend to maintain the
> package in DPMT.
Why can't python-crypt
of the ipaddress module from Python 3.3
This is a new dependency of python-cryptography. I intend to maintain the
package in DPMT.
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archi
course it will not work. So
I also added the following quilt patch:
-d/p/disable-python34.patch-
Description: Raise an ImportError when trying to import genshi in a
Python > 3.3, since it is not yet compatible with Python 3.4.
Remove this when upstream ticket 582 is resolved.
http
On May 01, 2012, at 11:37 AM, Scott Kitterman wrote:
>On Tuesday, May 01, 2012 10:45:24 AM Barry Warsaw wrote:
>...
>> The ipaddr library is as well, though that might get the "provisional"
>> tag.
>...
>This is one I'll need to keep an eye on as ipaddr is packaged in dpmt as a
>seperate module
On Tuesday, May 01, 2012 10:45:24 AM Barry Warsaw wrote:
...
> The ipaddr library is as well, though that might get the "provisional"
> tag.
...
This is one I'll need to keep an eye on as ipaddr is packaged in dpmt as a
seperate module (maintained by me). Upstream has a separate release that's
I just wanted to make people aware of the upstream Python 3.3 schedule. 3.3
alpha 3 was tagged today and we're less than two months away from beta 1.
Georg Brandl (the 3.3 release manager) sent out this message today:
http://mail.python.org/pipermail/python-dev/2012-May/119157.html
PE
26 matches
Mail list logo
