Re: Proposed update to the python policy

2007-03-22 Thread Josselin Mouette
Le mercredi 21 mars 2007 à 19:13 -0700, Steve Langasek a écrit : > You implemented a tool that *ignored* some of the use cases that went into > the initial policy, among them the case for 'current'. This is wrong. Python-support doesn't rely on anything else than what the maintainer chooses to bui

Re: Proposed update to the python policy

2007-03-22 Thread Mikhail Gusarov
Twas brillig at 19:13:19 21.03.2007 UTC-07 when Steve Langasek did gyre and gimble: SL> You implemented a tool that *ignored* some of the use cases that went into SL> the initial policy, among them the case for 'current'. Please, give us a link to the *written* use cases, so we can map them t

Re: Proposed update to the python policy

2007-03-22 Thread Tristan Seligmann
* Pierre Habouzit <[EMAIL PROTECTED]> [2007-03-21 21:49:00 +0100]: > On Wed, Mar 21, 2007 at 09:25:52PM +0100, Piotr Ożarowski wrote: > > it's useful for Python applications that need specific Python version. > > > > f.e. if current Python version is 2.4 and my app. will work only with > > python

Re: Proposed update to the python policy

2007-03-22 Thread Piotr Ożarowski
[Tristan Seligmann, 22.03.2007] > * Pierre Habouzit <[EMAIL PROTECTED]> [2007-03-21 21:49:00 +0100]: > > On Wed, Mar 21, 2007 at 09:25:52PM +0100, Piotr Ożarowski wrote: > > > it's useful for Python applications that need specific Python version. > > > > > > f.e. if current Python version is 2.4 a

Re: Proposed update to the python policy

2007-03-22 Thread Pierre Habouzit
On Thu, Mar 22, 2007 at 01:36:08PM +0100, Piotr Ożarowski wrote: > [Tristan Seligmann, 22.03.2007] > > * Pierre Habouzit <[EMAIL PROTECTED]> [2007-03-21 21:49:00 +0100]: > > > On Wed, Mar 21, 2007 at 09:25:52PM +0100, Piotr Ożarowski wrote: > > > > it's useful for Python applications that need spec

Re: Bug#415844: ITP: python-fpconst -- Utilities for handling IEEE 754 floating point special values

2007-03-22 Thread Stefano Zacchiroli
On Thu, Mar 22, 2007 at 04:20:01PM +0100, Bernd Zeimetz wrote: > The fpconst module is packaged within the python-soappy package at the > moment, which I have adopted with Ed Boraas' agreement. There're a few > reasons to package the small module as an extra package: Aaarrrggghhh! Just these days

Re: Bug#415844: ITP: python-fpconst -- Utilities for handling IEEE 754 floating point special values

2007-03-22 Thread Bernd Zeimetz
Heya, > > Just these days I've hijacked the python-soappy package, with the > agreement of the python-modules team since Ed did not reply to their > ping a long time ago. > > See http://lists.debian.org/debian-python/2007/03/msg00042.html. > He had replied to me within a few days, I missed to po

Re: Bug#415844: ITP: python-fpconst -- Utilities for handling IEEE 754 floating point special values

2007-03-22 Thread Stefano Zacchiroli
On Thu, Mar 22, 2007 at 05:30:54PM +0100, Bernd Zeimetz wrote: > > See http://lists.debian.org/debian-python/2007/03/msg00042.html. > He had replied to me within a few days, I missed to post it to d-py, though. Here it is: http://lists.debian.org/debian-python/2006/07/msg00022.html Hi discusse

Re: Proposed update to the python policy

2007-03-22 Thread Josselin Mouette
Le jeudi 22 mars 2007 à 14:50 +0100, Pierre Habouzit a écrit : > exactly, putting current is just yet-another-place where the > maintainers declares that he will only prepare the package for "current" > python. And you're right, python-(all-?)-dev is a already here to give a > hint to the dh_tool

Re: Proposed update to the python policy

2007-03-22 Thread Pierre Habouzit
On Thu, Mar 22, 2007 at 07:50:35PM +0100, Josselin Mouette wrote: > Le jeudi 22 mars 2007 à 14:50 +0100, Pierre Habouzit a écrit : > > exactly, putting current is just yet-another-place where the > > maintainers declares that he will only prepare the package for "current" > > python. And you're r

Re: Proposed update to the python policy

2007-03-22 Thread Josselin Mouette
Le jeudi 22 mars 2007 à 19:56 +0100, Pierre Habouzit a écrit : > > Just nitpicking: the dh_ tool doesn't need to know that, as it can guess > > it from what was previously built. This is a hint for the release > > managers (to know which packages need a binNMU), and could be the base > > for a scri

Re: Proposed update to the python policy

2007-03-22 Thread Piotr Ożarowski
[Josselin Mouette, 22.03.2007] > Le jeudi 22 mars 2007 à 19:56 +0100, Pierre Habouzit a écrit : > > > Just nitpicking: the dh_ tool doesn't need to know that, as it can guess > > > it from what was previously built. This is a hint for the release > > > managers (to know which packages need a binNMU

Re: Proposed update to the python policy

2007-03-22 Thread Pierre Habouzit
On Thu, Mar 22, 2007 at 10:13:40PM +0100, Piotr Ożarowski wrote: > [Josselin Mouette, 22.03.2007] > > Le jeudi 22 mars 2007 à 19:56 +0100, Pierre Habouzit a écrit : > > > > Just nitpicking: the dh_ tool doesn't need to know that, as it can guess > > > > it from what was previously built. This is a

Re: Proposed update to the python policy

2007-03-22 Thread Steve Langasek
On Thu, Mar 22, 2007 at 01:36:08PM +0100, Piotr Ożarowski wrote: > [Tristan Seligmann, 22.03.2007] > > * Pierre Habouzit <[EMAIL PROTECTED]> [2007-03-21 21:49:00 +0100]: > > > On Wed, Mar 21, 2007 at 09:25:52PM +0100, Piotr Ożarowski wrote: > > > > it's useful for Python applications that need spec