Python module packaging

2015-08-19 Thread olivier sallou
Hi,
I'd like to simple package python-eta module[0].
Having a look at policy, I only see SVN repo [1]. Can't we package module
using a git repo ?

Thanks

Olivier

[0] https://github.com/mbreese/eta/
[1] https://wiki.debian.org/Teams/PythonModulesTeam


Re: Python module packaging

2015-08-19 Thread Barry Warsaw
On Aug 19, 2015, at 07:41 PM, olivier.sal...@codeless.fr wrote:

As I am not a regular contributor to the python-modules (only made a few),
would you want to review the package once in git (when ready) before I upload
?  Or should I go when ready ? after reading again Python Policy of course
;-)

See also https://wiki.debian.org/Python/LibraryStyleGuide

But I'm sure someone here will be happy to review the package once it's
ready.

Cheers,
-Barry



Re: Python module packaging

2015-08-19 Thread Barry Warsaw
On Aug 19, 2015, at 12:43 PM, Barry Warsaw wrote:

On Aug 19, 2015, at 04:11 PM, olivier sallou wrote:

I'd like to simple package python-eta module[0].  Having a look at policy,
I only see SVN repo [1]. Can't we package module using a git repo ?

We are very close to switching to git.  I'm hoping it might actually happen
during Debconf, or soon thereafter.

https://wiki.debian.org/Python/GitPackaging

Cheers,
-Barry



Re: Removing some python3-* packages

2015-08-19 Thread Matthias Klose
On 07/09/2015 12:25 PM, Robert Collins 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 think it does. You are confusing here your role as an upstream Python author,
as a third party upstream developer and as a Debian developer.

As an upstream Python author you are actively forking the Python standard
library.  I don't think I read any PEP about these forks.

As a third party upstream developer (I assume openstack in this case) you want
to provide a way to port this stack to Python3. Having these modules available
for Python2 makes sense, but using these modules for Python3 is just a lazy way.

As a Debian developer you are duplicating code, and no, I don't think that
providing this code under a different name is different enough to rectify
distribution of this code in Debian.

In the past, the use of modules added in the standard library was handled like:

try:
  import module in stdlib
except ImportError:
  import separate module as module in stdlib

From my point of view this should be done with your python3 modules as well. As
a service to the community you could provide appropriate snippets like the above
as well. maybe adjusted for different Python versions.

Further, if your forks gain popularity, there's no way out to remove these at
some time, because people will rely on these forks, having no way out of using
these modules, obsoleting the versions in the standard library, and people will
be stuck with your forks.

So please remove the python3 versions at least for Debian. I will definitely ask
for their removal, and will add appropriate Conflicts/Replaces once 3.5 becomes
the default in Debian.

Matthias



Re: Python module packaging

2015-08-19 Thread olivier.sal...@codeless.fr


On 08/19/2015 06:44 PM, Barry Warsaw wrote:
 On Aug 19, 2015, at 12:43 PM, Barry Warsaw wrote:

 On Aug 19, 2015, at 04:11 PM, olivier sallou wrote:

 I'd like to simple package python-eta module[0].  Having a look at policy,
 I only see SVN repo [1]. Can't we package module using a git repo ?
 We are very close to switching to git.  I'm hoping it might actually happen
 during Debconf, or soon thereafter.
Ok, package is not an urgent matter, so I propose to wait a little.

As I am not a regular contributor to the python-modules (only made a
few), would you want to review the package once in git (when ready)
before I upload ?
Or should I go when ready ? after reading again Python Policy of course ;-)

Olivier
 https://wiki.debian.org/Python/GitPackaging

 Cheers,
 -Barry


 -- 
 gpg key id: 4096R/326D8438  (keyring.debian.org)
 Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438



mass-bug filling proposal: missing dh-python build dependency

2015-08-19 Thread Piotr Ożarowski
Hi,

I checked¹ logs from gcc rebuild² and it looks like almost 500 packages
are still missing dh-python build dependency even thought the warning is
there since a while.
(and I'd really love to remove old dh_python2 from python package)

Does someone want to prepare a patch for lintian to detect it or is it 
ok to do the mass bug filling?

In case of lintian, I guess it's enough to check if all packages that
use ${python:Depends}³ also build depend on dh-python

[¹] grep 'Please add dh-python package to Build-Depends' 
~doko/public_html/logs/gcc5-20150813/archive-gcc-08-13-2015/* 
[²] https://people.debian.org/~doko/logs/gcc5-20150813/archive-gcc-08-13-2015/
[³] or ${python3:Depends} or ${pypy:Depends}, but these are not included in
attached list
-- 
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
Adam C. Powell, IV hazel...@debian.org
   aster (U)

A Mennucc1 mennu...@debian.org
   kaa-base (U)
   kaa-imlib2 (U)
   kaa-metadata (U)
   pygame (U)

A. Maitland Bottoms bott...@debian.org
   quisk

Aaron M. Ucko u...@debian.org
   bitpim

Adam C. Powell, IV hazel...@debian.org
   pysparse

Adrian Knoth a...@drcomp.erfurt.thur.de
   a2jmidid (U)

Alastair McKinstry mckins...@debian.org
   cmor
   silo-llnl
   spherepack

Albert Huang alb...@csail.mit.edu
   pybluez (U)

Alessandro Ghedini gh...@debian.org
   ecasound (U)

Alessio Treglia ales...@debian.org
   a2jmidid (U)
   font-manager
   gnome-commander (U)
   idjc (U)
   jack-mixer (U)
   ladish (U)
   mididings (U)
   python-gudev

Alexander Dreyer adre...@gmx.de
   polybori (U)

Alexander Sack a...@jwsdot.com
   gnash (U)

Alexander Zangerl a...@debian.org
   duplicity

Alexandre Fayolle afayo...@debian.org
   python-scipy (U)

Allison Randal alli...@lohutok.net
   4digits (U)

Ana Beatriz Guerrero Lopez a...@debian.org
   imdbpy

Andrea Colangelo war...@ubuntu.com
   font-manager (U)

Andrea Gasparini ga...@yattaweb.it
   python-poppler

Andrea Palazzi palazziand...@yahoo.it
   aster (U)

Andreas Henriksson andr...@fatal.se
   caribou (U)
   gconf (U)
   glib2.0 (U)
   gobject-introspection (U)
   pygtk (U)
   totem (U)

Andreas Tille ti...@debian.org
   arden (U)
   cain (U)
   fitgcp (U)
   gasic (U)
   gdcm (U)
   genometools (U)
   htseq (U)
   invesalius (U)
   kissplice (U)
   librcsb-core-wrapper (U)
   macs (U)
   pdb2pqr (U)
   python-casmoothing (U)
   python-qcli (U)
   qiime (U)
   visionegg (U)
   vxl (U)

Andrew Chadwick a.t.chadw...@gmail.com
   mypaint (U)

Andrew Shadura andre...@debian.org
   wmii

Andrew Starr-Bochicchio a...@debian.org
   keybinder
   libtorrent-rasterbar (U)

Android tools Maintainer android-tools-de...@lists.alioth.debian.org
   android-tools

Anibal Monsalve Salazar ani...@debian.org
   cluster-glue (U)
   heartbeat (U)
   pacemaker (U)
   pcp (U)

Antoine Beaupré anar...@debian.org
   photofloat

Anton Gladky gl...@debian.org
   freefoam (U)
   gmsh (U)
   minieigen (U)
   pygts (U)
   pysph (U)
   python-demgengeo (U)

Antonio Valentino antonio.valent...@tiscali.it
   pykdtree (U)

Apollon Oikonomopoulos apoi...@debian.org
   ganeti (U)
   python-hiredis (U)

Ari Pollak a...@debian.org
   gimp

Arnaud Fontaine ar...@debian.org
   cheetah
   pcapy
   pyme
   zope2.13 (U)

Arnaud Quette aque...@debian.org
   pigment-python (U)
   pylirc (U)

Arne Bernin a...@alamut.de
   libfreenect (U)

Arno Töll a...@debian.org
   xnbd

Aron Xu a...@debian.org
   ibus-libpinyin (U)
   libxml2 (U)
   libxslt (U)
   python-jswebkit

Arthur de Jong adej...@debian.org
   nss-pam-ldapd

Arturo Borrero Gonzalez arturo.borrero.g...@gmail.com
   suricata (U)

Asheesh Laroia ashe...@asheesh.org
   liblicense

Asias He asias.he...@gmail.com
   input-pad (U)

Asias He as...@debian.org
   ibus-libpinyin (U)
   opencc (U)

Aurelien Jarno aure...@debian.org
   i2c-tools
   libftdi

Barry deFreese bdefre...@debian.org
   adonthell (U)
   monsterz (U)

Baruch Even bar...@debian.org
   hocr (U)
   libhdate (U)
   pyfribidi (U)

Bastian Blank wa...@debian.org
   linux-latest (U)
   linux-tools (U)
   mklibs (U)

Bastian Kleineidam cal...@debian.org
   linkchecker

Bdale Garbee bd...@gag.com
   chirp (U)

Ben Armstrong sy...@sanctuary.nslug.ns.ca
   xpilot-ng

Ben Carrillo b...@futeisha.org
   python-srp

Ben Finney ben+deb...@benfinney.id.au
   python-coverage

Ben Hutchings b...@decadent.org.uk
   linux-latest (U)
   linux-tools (U)

Ben Pfaff pfaff...@debian.org
   openvswitch (U)

Benedict Verhegghe benedict.verheg...@ugent.be
   pyformex

Benjamin Drung bdr...@debian.org
   distro-info
   xmms2

Bernd Zeimetz b...@debian.org
   gimp-plugin-registry
   gimp-plugin-registry (U)
   gpsd
   nagios-plugins-contrib (U)
   pyicu (U)
   python-gnutls (U)
   pyxmpp (U)
   rhn-client-tools

Bert Agaz berta...@ptitcanardnoir.org
   pycryptopp
   zfec

Brian May b...@debian.org
   billiard (U)