Re: Source package name with python- or without?

2015-06-08 Thread Piotr Ożarowski
[Tim Landscheidt, 2015-06-08]
 Should source package names (Source: in debian/control) be
 prefixed with python-?

no.

I use python- prefix for source package name only if the name is
not unique enough.
-- 
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl  www.griffith.cc   www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645


-- 
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/20150608061301.go11...@sar0.p1otr.com



Re: Source package name with python- or without?

2015-06-08 Thread Barry Warsaw
On Jun 08, 2015, at 08:13 AM, Piotr Ożarowski wrote:

I use python- prefix for source package name only if the name is
not unique enough.

Same.
-Barry



pgpBpCZep6NyA.pgp
Description: OpenPGP digital signature


Re: Bug#785275: ITP: python-ipaddress -- Backport of the ipaddress module from Python 3.3

2015-06-08 Thread Tristan Seligmann
On Mon, 8 Jun 2015 at 15:27 Tristan Seligmann mithra...@mithrandi.net
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 stdin, line 1, in module
   File
 /home/mithrandi/deployment/virtualenvs/tempenv-56cd218832e2d/local/lib/python2.7/site-packages/ipaddr.py,
 line 78, in IPAddress
 address)
 ValueError: '\x7f\x00\x00\x01' does not appear to be an IPv4 or IPv6
 address


For a more obnoxious example:

 import ipaddress, ipaddr
 ipaddress.ip_address(b'0::1')
IPv4Address(u'48.58.58.49')
 ipaddr.IPAddress(b'0::1')
IPv6Address('::1')


Re: Bug#785275: ITP: python-ipaddress -- Backport of the ipaddress module from Python 3.3

2015-06-08 Thread Tristan Seligmann
Control: tag -1 - wontfix

On Fri, 22 May 2015 at 17:06 Scott Kitterman deb...@kitterman.com 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 which affects
python-cryptography:

 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 stdin, line 1, in module
  File
/home/mithrandi/deployment/virtualenvs/tempenv-56cd218832e2d/local/lib/python2.7/site-packages/ipaddr.py,
line 78, in IPAddress
address)
ValueError: '\x7f\x00\x00\x01' does not appear to be an IPv4 or IPv6 address

The reason is that ipaddr requires you to use the ipaddr.Bytes wrapper
type, rather than a normal bytes object, for packed addresses. Closer
examination reveals that the entire module appears to be API-incompatible
with ipaddress with regard to string types; ipaddress expects to receive
unpacked addresses as unicode objects, but ipaddr expects them as bytes
(not Bytes) objects. This break in compatibility probably goes unnoticed in
most situations due to implicit encoding/decoding, but at this point I am
seriously uncomfortable trying to work around these API differences in a
patch to cryptography (or any other future package I work on that depends
on ipaddress, for that matter). Thus I am renewing my intention to package
python-ipaddress for use as a dependency of python-cryptography.