Re: python packaging infrastructure

2006-01-13 Thread Joe Wreschnig
On Fri, 2006-01-13 at 12:44 +0100, Matthias Klose wrote: > Joe Wreschnig writes: > > One issue that comes to my mind now is behavior with regards to > > dpkg-divert. I've diverted a number of Python modules on my system; > > under this centralized registry I would have to divert them for all > > ve

Re: python packaging infrastructure

2006-01-13 Thread Joey Hess
Matthias Klose wrote: > Josselin Mouette writes: > > Furthermore, if you want to see this implemented, you'll have to find > > someone else to write the necessary changes to dh_python. I will not > > write nor maintain any code that parses the control file in dh_python. > > This script is already o

Re: python packaging infrastructure

2006-01-13 Thread Matthias Klose
Josselin Mouette writes: > Furthermore, if you want to see this implemented, you'll have to find > someone else to write the necessary changes to dh_python. I will not > write nor maintain any code that parses the control file in dh_python. > This script is already one of the most complex ones in d

Re: python packaging infrastructure

2006-01-13 Thread Matthias Klose
Josselin Mouette writes: > Le vendredi 13 janvier 2006 à 12:28 +0100, Matthias Klose a écrit : > > > I don't understand the *need* for a specific control field. I just see > > > it as another way to implement dh_python. My opinion is that > > > "dh_python -m 2.2" is easier to implement and looks m

Re: python packaging infrastructure

2006-01-13 Thread Josselin Mouette
Le vendredi 13 janvier 2006 à 12:28 +0100, Matthias Klose a écrit : > > I don't understand the *need* for a specific control field. I just see > > it as another way to implement dh_python. My opinion is that > > "dh_python -m 2.2" is easier to implement and looks more like other dh_* > > commands

Re: python packaging infrastructure

2006-01-13 Thread Matthias Klose
Joe Wreschnig writes: > On Fri, 2006-01-13 at 12:04 +0100, Matthias Klose wrote: > > Joe Wreschnig writes: > > > On Thu, 2006-01-12 at 14:44 +0100, Matthias Klose wrote: > > > >- modules are installed into a directory not directly in sys.path. > > > > > > While I understand the rationale here,

Re: python packaging infrastructure

2006-01-13 Thread Matthias Klose
Josselin Mouette writes: > Le vendredi 13 janvier 2006 à 11:30 +0100, Matthias Klose a écrit : > > > Having a new field in the control file diverges from how debhelper > > > programs usually behave, so I'd like to avoid such a solution - and I > > > don't think there's a need for it. > > > > I did

Re: python packaging infrastructure

2006-01-13 Thread Joe Wreschnig
On Fri, 2006-01-13 at 12:04 +0100, Matthias Klose wrote: > Joe Wreschnig writes: > > On Thu, 2006-01-12 at 14:44 +0100, Matthias Klose wrote: > > >- modules are installed into a directory not directly in sys.path. > > > > While I understand the rationale here, this could be *very* confusing >

Re: python packaging infrastructure

2006-01-13 Thread Matthias Klose
Joe Wreschnig writes: > On Thu, 2006-01-12 at 14:44 +0100, Matthias Klose wrote: > >- modules are installed into a directory not directly in sys.path. > > While I understand the rationale here, this could be *very* confusing > for people coming to Debian from other operating systems. People w

Re: Ending/reducing bytecode compilation, loosening dependencies

2006-01-13 Thread Joe Wreschnig
On Fri, 2005-12-30 at 12:33 -0600, Joe Wreschnig wrote: > 1. Stop compiling .pyo files, entirely (I'm hoping for little argument > on this). > > Rationale: .pyo files are a joke. They aren't optimized in any > meaningful sense, they just have asserts removed. Examples for several > non-trivial fil

Re: python packaging infrastructure

2006-01-13 Thread Josselin Mouette
Le vendredi 13 janvier 2006 à 11:30 +0100, Matthias Klose a écrit : > > Having a new field in the control file diverges from how debhelper > > programs usually behave, so I'd like to avoid such a solution - and I > > don't think there's a need for it. > > I did outline the need for it. And I see

Re: python packaging infrastructure

2006-01-13 Thread Joe Wreschnig
On Fri, 2006-01-13 at 11:05 +0100, Josselin Mouette wrote: > Le vendredi 13 janvier 2006 à 00:33 -0600, Joe Wreschnig a écrit : > > > - Some concerns were raised by the release team, that python-support > > > tracks it's own state instead of using the dpkg database. To keep > > > track of usable

Re: python packaging infrastructure

2006-01-13 Thread Matthias Klose
Josselin Mouette writes: > Le vendredi 13 janvier 2006 à 00:33 -0600, Joe Wreschnig a écrit : > > > - Some concerns were raised by the release team, that python-support > > > tracks it's own state instead of using the dpkg database. To keep > > > track of usable python versions, python-central u

Re: python packaging infrastructure

2006-01-13 Thread Josselin Mouette
Le vendredi 13 janvier 2006 à 00:33 -0600, Joe Wreschnig a écrit : > > - Some concerns were raised by the release team, that python-support > > tracks it's own state instead of using the dpkg database. To keep > > track of usable python versions, python-central uses a field > > Python-Version i