Re: Removing some python3-* packages

2015-07-09 Thread Barry Warsaw
On Jul 09, 2015, at 10:25 PM, Robert Collins wrote:

I don't have a view on other packages.

As it turns out, enum34 is actually renaming its public package name so it
won't conflict with the stdlib name.  I may end up keeping the python3 variant
after all.

Cheers,
-Barry


-- 
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/20150709094914.2a937...@limelight.wooz.org



Re: Sphinx 1.3 in Debian experimental

2015-07-09 Thread Dmitry Shachnev
Hi,

On Wed, 08 Jul 2015 15:11:18 +0300, Dmitry Shachnev wrote:
 I will write a patch to add support for this to Sphinx when I have time.

Here it is: https://github.com/sphinx-doc/sphinx/pull/1954

Will upload it to Debian when it is acknowledged by upstream.

--
Dmitry Shachnev

signature.asc
Description: OpenPGP digital signature


Re: Removing some python3-* packages

2015-07-09 Thread Ian Cordasco
On Jul 9, 2015 5:25 AM, Robert Collins robe...@robertcollins.net wrote:

 On 3 July 2015 at 08:29, Scott Kitterman deb...@kitterman.com wrote:

  I think dropping these duplicates is the only thing that makes sense.
For
  reference, I dropped python3-ipaddr once python3.2 was gone (because
3.3 has
  ipaddress, which does the same thing).

 Where its a dupe sure.

 unittest2, traceback2, linecache2, mock are not duplicates of the
 functionality in 3.4 - they are backports of things in 3.5 (to all
 pythons). And they will shortly have more than 3.5 itself has in it,
 as they are rolling backports: what lands in 3.6 will go into them. So
 I don't think removing them makes sense.

 I don't have a view on other packages.

 -Rob

 --
 Robert Collins rbtcoll...@hp.com
 Distinguished Technologist
 HP Converged Cloud


 --
 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/CAJ3HoZ0a9rSSAc-zv+7qhP+0n-wMGQ=hrm__togtuesopuk...@mail.gmail.com


Further, should API compatibility also be considered? If I remember
correctly ipaddress in the stdlib and ipaddr have similar but not exactly
identical APIs


Key package: update of unittest2 testtools in Experimental needs approval

2015-07-09 Thread Thomas Goirand
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear FTP masters,

I have uploaded recently (yesterday and today):
- - unittest2 with added Py3 support
- - python-linecache2
- - python-traceback2
- - python-testtools

The new Unittest2 needs python-traceback2 which is in the NEW queue.
Testtools needs linecache2 and traceback2.

It'd be nice if the above packages could be approved soon, as they are
key (build) dependencies which we need for all of the other packages.

Because unittest2 in Experimental (which I uploaded prior to adding Py3
support) depends on python-traceback2, it is currently broken, which is
also a reason why it'd be nice to have python-traceback2 reviewed and
approved.

Unittest2 is used almost everywhere in Py3 unit tests BTW.

Cheers,

Thomas Goirand (zigo)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJVnjzdAAoJENQWrRWsa0P+2XQP/R4gLePplo6gfDXb0cSVXXuq
utmoFYS8AMlJRoq68kzS1p5ZbaypEPiBW0tpdi18k8gldJbq1QBoWqOf6hNvgQf6
tyReNEy3T43mPj9gQxmbgjWFtUtS5dIIzeljEvGAAQgad+5IKhrSonuDnXmd8erb
jU+O3M4cPcNbQQThtiLmLPZti7z+P/x9AzZpMFoQwAjAsTUj8PeOhPeDzMZAfsHM
iecbzEOwDHSHSjGRzm7o21tdJAt4JkwPfTdIablbMhnfRJft9Dw9Y3yDBSKci2oO
sQPACH5DzYKxVhKlPB3aUg6elIQaBVDOscd6F0uKSce8844U+Z7uUlrtegLRlfkM
VMSOtTskqsAhJSpeRVDppH8laevJPO+Vv+FhwWTkQJB05PZww00Rgte0jVdLzazf
bDyTkJ1S0uohhOH5ezOI3U+Qi/w7lZstODDTGl26U6i6eCbVAi3CTVG6SZUhJvyH
gleg4mmxaTY07PB89kTkykIVAL22oXLafzPLw5KEdmfqP/1+TquR5q00D0tgcSi1
+fPIjl9f4x7XYQwS7KAkNs6IYB2TzJoEgm7m1I9A9R2/X5Sx/jTQtL92c9EuVTwX
eMN2CurSUyhsOQ2sqMuWGQcrBRMKUXmpjMcMGc6mxl0Ce2N3FBqlcsWeqfNHAp5W
Kkhf8UQyCFgq39iHqDT8
=xZGJ
-END PGP SIGNATURE-


-- 
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/559e3ce4.4040...@debian.org



Re: Removing some python3-* packages

2015-07-09 Thread Robert Collins
On 3 July 2015 at 08:29, Scott Kitterman deb...@kitterman.com wrote:

 I think dropping these duplicates is the only thing that makes sense. For
 reference, I dropped python3-ipaddr once python3.2 was gone (because 3.3 has
 ipaddress, which does the same thing).

Where its a dupe sure.

unittest2, traceback2, linecache2, mock are not duplicates of the
functionality in 3.4 - they are backports of things in 3.5 (to all
pythons). And they will shortly have more than 3.5 itself has in it,
as they are rolling backports: what lands in 3.6 will go into them. So
I don't think removing them makes sense.

I don't have a view on other packages.

-Rob

-- 
Robert Collins rbtcoll...@hp.com
Distinguished Technologist
HP Converged Cloud


-- 
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/CAJ3HoZ0a9rSSAc-zv+7qhP+0n-wMGQ=hrm__togtuesopuk...@mail.gmail.com



Re: Removing some python3-* packages

2015-07-09 Thread Scott Kitterman


On July 9, 2015 7:39:15 AM EDT, Ian Cordasco graffatcolmin...@gmail.com wrote:
On Jul 9, 2015 5:25 AM, Robert Collins robe...@robertcollins.net
wrote:

 On 3 July 2015 at 08:29, Scott Kitterman deb...@kitterman.com
wrote:

  I think dropping these duplicates is the only thing that makes
sense.
For
  reference, I dropped python3-ipaddr once python3.2 was gone
(because
3.3 has
  ipaddress, which does the same thing).

 Where its a dupe sure.

 unittest2, traceback2, linecache2, mock are not duplicates of the
 functionality in 3.4 - they are backports of things in 3.5 (to all
 pythons). And they will shortly have more than 3.5 itself has in it,
 as they are rolling backports: what lands in 3.6 will go into them.
So
 I don't think removing them makes sense.

 I don't have a view on other packages.

 -Rob


Further, should API compatibility also be considered? If I remember
correctly ipaddress in the stdlib and ipaddr have similar but not
exactly
identical APIs

I dropped python3-ipaddr only after all the reverse-depends were ported to use 
ipaddress from the stdlib.  So I agree it should be considered and it was.

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/2bbc7d70-567d-4d8b-ab9c-06bce1915...@kitterman.com