rejoindre l'équip e d'empaquetage python

2006-06-14 Thread Alexandre Fayolle
Hi everyone I would be glad to join the python-modules packaging team. My alioth login is afayolle, and for those who dwell there, my irc nick is agurney. Thanks, -- Alexandre Fayolle LOGILAB, Paris (France) Formations Python, Zope, Plone, Debian: http://www.log

joining the python-modules team

2006-06-14 Thread Alexandre Fayolle
Apologies for the French subject line in the previous mail. I'm resending in case it caused it to be trapped by spam filters. I would be glad to join the python-modules packaging team. My alioth login is afayolle, and for those who dwell there, my irc nick is agurney. Thanks, -- Alexandre F

Re: joining the python-modules team

2006-06-14 Thread Raphael Hertzog
Hi, On Wed, 14 Jun 2006, Alexandre Fayolle wrote: > Apologies for the French subject line in the previous mail. I'm > resending in case it caused it to be trapped by spam filters. > > I would be glad to join the python-modules packaging team. Welcome to the group! You have been added and you w

Bugs have been filed, work can begin

2006-06-14 Thread Raphael Hertzog
On Tue, 13 Jun 2006, Raphael Hertzog wrote: > Here's a list of sources packages that need to be updated (266 packages): > http://people.debian.org/~hertzog/python/sources-by-maint Pierre Habouzit (Madcoder) did the mass-bug filing: http://bugs.debian.org/submitter:[EMAIL PROTECTED] http://bugs.de

Re: Coordinated effort to update python packages

2006-06-14 Thread Pierre Habouzit
Le Mar 13 Juin 2006 20:38, Raphael Hertzog a écrit : > For NMUers, always start by filling a bug report refering to this > announce, register the bug number and your intent to work on it in > the wiki page, do the work, send the patch to the BTS and upload the > package appropriately (using a DELA

request for NMUs [Was: Coordinated effort to update python packages]

2006-06-14 Thread Robert Jordens
Hello! [Tue, 13 Jun 2006] Raphael Hertzog wrote: > If you don't have time to do this now, please reply on > debian-python@lists.debian.org and allow us to make NMU of your packages. I wont have much time to fix my packages so please feel free to NMU any of them: > Robert Jordens <[EMAIL PROTECTE

Re: New python distutils class

2006-06-14 Thread Raphael Hertzog
On Wed, 14 Jun 2006, Marc Dequènes wrote: > They all are available in unstable now. You can find in my web directory > 2 examples (soya and editobj), where, besides bugs in pysupport or > pycentral, are well built using an updated version of the class : > http://perso.duckcorp.org/duck/python-new

Re: Bugs have been filed, work can begin

2006-06-14 Thread Vincent Danjean
Raphael Hertzog wrote: > On Tue, 13 Jun 2006, Raphael Hertzog wrote: >> Here's a list of sources packages that need to be updated (266 packages): >> http://people.debian.org/~hertzog/python/sources-by-maint > > Pierre Habouzit (Madcoder) did the mass-bug filing: > http://bugs.debian.org/submitter:

question about the new policy

2006-06-14 Thread Pierre Habouzit
let's imagine we have that case: python-foo is a python module that uses and needs features from python2.X. python-bar uses python-foo but can work with all 2.* python version. Python-Versions will be: * >= 2.X for python-foo * all for python-bar how do we ensure that a user that has a pytho

Re: question about the new policy

2006-06-14 Thread Raphael Hertzog
On Wed, 14 Jun 2006, Pierre Habouzit wrote: > let's imagine we have that case: > > python-foo is a python module that uses and needs features from > python2.X. python-bar uses python-foo but can work with all 2.* python > version. > > Python-Versions will be: > * >= 2.X for python-foo > * all

Re: Coordinated effort to update python packages

2006-06-14 Thread Frederic Peters
Frank Lichtenheld wrote: > My libgpod package didn't appear in the list because it currently only > builds an python2.3-gpod and no python-gpod at all. Feel free to NMU > this package as I really have no idea about that whole python modules My python2.3-lasso package didn't appear either; I shoul

Re: Bugs have been filed, work can begin

2006-06-14 Thread Joe Wreschnig
On Wed, 2006-06-14 at 11:55 +0200, Raphael Hertzog wrote: > On Tue, 13 Jun 2006, Raphael Hertzog wrote: > > Here's a list of sources packages that need to be updated (266 packages): > > http://people.debian.org/~hertzog/python/sources-by-maint > > Pierre Habouzit (Madcoder) did the mass-bug filing

Re: Bugs have been filed, work can begin

2006-06-14 Thread Pierre Habouzit
Le mer 14 juin 2006 19:27, Joe Wreschnig a écrit : > On Wed, 2006-06-14 at 11:55 +0200, Raphael Hertzog wrote: > > On Tue, 13 Jun 2006, Raphael Hertzog wrote: > > > Here's a list of sources packages that need to be updated (266 > > > packages): > > > http://people.debian.org/~hertzog/python/sources

Re: Bug#373537: python-gd may need an upgrade to the new Python Policy

2006-06-14 Thread Ben Pfaff
"Python Transition Mass bug" <[EMAIL PROTECTED]> writes: > Hi, your package has been detected as generating a python > module/extension that may need an upgrade to the new Python Policy[1]. > > A wiki page [2] explains what has to be done to upgrade your packages > to the new Policy. This bug

please nmu python-orbit

2006-06-14 Thread Tom Cato Amundsen
Hello, can someone please nmu python-orbit to comply with the new python policy? The bug is #373331. I'm too buzy, and going on vacation now. If someone want to adopt the package, they are welcome to take it. -- Tom Cato Amundsen <[EMAIL PROTECTED]> http://www.solfege.org/ GNU Sol

Re: Coordinated effort to update python packages

2006-06-14 Thread Mike Hommey
On Tue, 13 Jun 2006 at 16:10:48 -0500, Joe Wreschnig wrote: > On Tue, 2006-06-13 at 22:05 +0200, Mike Hommey wrote: > > What about people who want to use pyxpcom with modules that aren't > > available with the current python ? > > But a user couldn't install more than one such module at a time, si

Re: Coordinated effort to update python packages

2006-06-14 Thread Graham Wilson
On Tue, Jun 13, 2006 at 11:43:21PM +0200, Piotr Ozarowski wrote: > Graham Wilson ([EMAIL PROTECTED]): > > That would happen anyway for new Python releases, plus, my understanding > > is that with the new Python framework in place, supporting new Python > > versions can be handled simply by bin NMUs

Re: Coordinated effort to update python packages

2006-06-14 Thread Piotr Ozarowski
Graham Wilson ([EMAIL PROTECTED]): > > What if user will change his default python version (f.e. if his scripts > > will use /usr/bin/env python, or simply he will start his script with > > pythonX.Y)? > > I'm not sure I understand your question. Why would the user change his > default Python vers

Re: Coordinated effort to update python packages

2006-06-14 Thread Graham Wilson
On Tue, Jun 13, 2006 at 11:45:32PM +0200, Matthias Klose wrote: > that is correct. OTOH, each new upload to unstable may add a new > dependency on a newly uploaded library having a more strict dependency > or a new soname. If you build for the version we transition from, and > for the version we tr

Re: Coordinated effort to update python packages

2006-06-14 Thread Graham Wilson
On Wed, Jun 14, 2006 at 11:06:53PM +0200, Piotr Ozarowski wrote: > He can simply change /usr/bin/python symlink (that's very bad, but > it's possible) To be honest, I don't think it's worth supporting that, since the user is basically breaking his Python install. > or if he will need some feature

Re: Coordinated effort to update python packages

2006-06-14 Thread Jed Frechette
Piotr Ozarowski <[EMAIL PROTECTED]> wrote: > > > What if user will change his default python version (f.e. if his > > > scripts will use /usr/bin/env python, or simply he will start his > > > script with pythonX.Y)? > > > > I'm not sure I understand your question. Why would the user change his > >

Re: Coordinated effort to update python packages

2006-06-14 Thread Graham Wilson
On Wed, Jun 14, 2006 at 06:43:32PM -0600, Jed Frechette wrote: > This is exactly the situation I am in now. I want to use PyX for > plotting but I need some of the features in Python 2.4. Well I > probably don't need them, I am sure I could find work arounds, but why > should I write code that is m