Hi,
On Wed, 14 Jun 2006, Simon McVittie wrote:
> Hi,
> I'd like to join the python-modules team, in order to co-maintain
> python-docutils with Martin F. Krafft. My Alioth login is smcv-guest.
Welcome to the group! You have been added, you will have commit rights
tomorrow.
Cheers,
--
Raphaël He
On Wed, 14 Jun 2006, Marc Dequènes wrote:
> > - Perhaps in keeping with the style of cdbs, it would be better to have
> > two classes python-pycentral and python-pysupport (and some
> > python-common or python-core) behind it? This would also avoid the
> > tacky use of -ng in the class name. :-
On Tue, Jun 13, 2006 at 08:38:57PM +0200, Raphael Hertzog wrote:
> the Python team has agreed on a new policy [1]. As we want to do the
> python 2.4 transition now, we need to make sure the packages match the
> policy. This will limit the amount of broken packages when python2.4 will
> become the d
On Tue, Jun 13, 2006 at 09:13:26PM +0200, Mike Hommey wrote:
> PS: Anyways, there's one package you didn't list because it's in NEW,
> which WON'T be merged as required by the new policy: python2.x-xpcom,
> provided by xulrunner.
> The reason is simple: different installations for different python
Joey Hess writes:
> I don't particularly mind that you've chosen to NMU debhelper. However,
> I can't guarantee that I will preserve the interfaces that you've added
> to dh_python in a backwards compatible way when I get around to looking
> at it.
>
> (FWIW, I began ignoring this issue when the p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I'd like to join the python-modules team, in order to co-maintain
python-docutils with Martin F. Krafft. My Alioth login is smcv-guest.
I'm currently preparing an upload which will fix some of the old bugs
and use the new Python policy.
Thanks,
Coin,
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> - Perhaps in keeping with the style of cdbs, it would be better to have
> two classes python-pycentral and python-pysupport (and some
> python-common or python-core) behind it? This would also avoid the
> tacky use of -ng in the class name
Mike Hommey writes:
> On Tue, Jun 13, 2006 at 09:55:08PM +0200, Raphael Hertzog <[EMAIL PROTECTED]>
> wrote:
> > When you install some python extensions (.so), it is common that they come
> > with
> > associated .py files (modules). Those .py files usually are the same in
> > /usr/lib/python2.3
Graham Wilson writes:
> On Tue, Jun 13, 2006 at 11:22:27PM +0200, Piotr Ozarowski wrote:
> > Graham Wilson ([EMAIL PROTECTED]):
> > > Speaking of this, I have a module (python-pyx) that I think is only used
> > > by end-users (not applications), so I think it makes sense to only
> > > install modul
Graham Wilson ([EMAIL PROTECTED]):
> On Tue, Jun 13, 2006 at 11:22:27PM +0200, Piotr Ozarowski wrote:
> > What if default python version will change? You will have to reupload
> > your package.
>
> That would happen anyway for new Python releases, plus, my understanding
> is that with the new Pyth
Le mardi 13 juin 2006 à 16:31 -0500, Graham Wilson a écrit :
> 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 in the case that I can't make
> an upload myse
On Tue, Jun 13, 2006 at 11:22:27PM +0200, Piotr Ozarowski wrote:
> Graham Wilson ([EMAIL PROTECTED]):
> > Speaking of this, I have a module (python-pyx) that I think is only used
> > by end-users (not applications), so I think it makes sense to only
> > install modules and extensions for the curren
Graham Wilson ([EMAIL PROTECTED]):
> Speaking of this, I have a module (python-pyx) that I think is only used
> by end-users (not applications), so I think it makes sense to only
> install modules and extensions for the current version. Does this make
> sense?
What if default python version will c
On Tue, Jun 13, 2006 at 09:55:08PM +0200, Raphael Hertzog wrote:
> OK, then indicate "current" in XS-Python-Version and support only the
> current version in python-xpcom (make sure to generate the provides
> field).
Speaking of this, I have a module (python-pyx) that I think is only used
by end-u
On Tue, 2006-06-13 at 22:05 +0200, Mike Hommey wrote:
> On Tue, Jun 13, 2006 at 09:55:08PM +0200, Raphael Hertzog <[EMAIL PROTECTED]>
> wrote:
> > When you install some python extensions (.so), it is common that they come
> > with
> > associated .py files (modules). Those .py files usually are th
On Tue, Jun 13, 2006 at 09:55:08PM +0200, Raphael Hertzog <[EMAIL PROTECTED]>
wrote:
> When you install some python extensions (.so), it is common that they come
> with
> associated .py files (modules). Those .py files usually are the same in
> /usr/lib/python2.3 and /usr/lib/python2.4, that's w
On Tue, 13 Jun 2006, Mike Hommey wrote:
> > So please check in the list at the end of this mail if you're concerned,
> > and if yes, please update your packages following these instructions:
> > http://wiki.debian.org/DebianPython/NewPolicy
> > http://people.debian.org/~piman/python-policy/
>
> Ma
Le mardi 13 juin 2006 à 15:23 -0400, Joey Hess a écrit :
> (FWIW, I began ignoring this issue when the politics and constant
> advocacy and pressure became too annoying to bother with, and I expect
> to ignore it for at least another couple of weeks. Unfortunatly that
> means that to avoid either t
* Mike Hommey ([EMAIL PROTECTED]) [060613 21:29]:
> PPS: I'll take care of libxml2 and libxslt as soon as I understand what
> I'm supposed to change.
Please don't upload libxml2 until the current version either hits
testing or is RC-buggy.
Thanks.
Cheers,
Andi
--
http://home.arcor.de/andrea
On Tue, Jun 13, 2006 at 08:38:57PM +0200, Raphael Hertzog <[EMAIL PROTECTED]>
wrote:
> Hello,
>
> the Python team has agreed on a new policy [1]. As we want to do the
> python 2.4 transition now, we need to make sure the packages match the
> policy. This will limit the amount of broken packages w
I don't particularly mind that you've chosen to NMU debhelper. However,
I can't guarantee that I will preserve the interfaces that you've added
to dh_python in a backwards compatible way when I get around to looking
at it.
(FWIW, I began ignoring this issue when the politics and constant
advocacy
On Tue, 13 Jun 2006, Raphael Hertzog wrote:
> Hi,
>
> I've prepared this:
> http://wiki.debian.org/DebianPython/NewPolicy
>
> Feel free to enhance.
>
> I also converted python-pam as an example (std debhelper package):
> http://people.debian.org/~hertzog/python/examples/
>
> I'll gladly put oth
On Tue, 13 Jun 2006, Raphael Hertzog wrote:
> Now it's time to ask all maintainers to update their packages. Someone
> should prepare several list of source packages:
> - python extensions
> - python modules only
> - python apps
>
> Then we need to fill bugs, and usertag them "policy-ext", "policy
Le samedi 10 juin 2006 à 16:24 +0200, Matthias Klose a écrit :
> As pointed out in [1], the split of a package (in the python sense)
> with extensions and modules into two different directories leads to
> a changed import order and should be avoided. I.e. this kind of
> package must be installed in
On Tue, 13 Jun 2006, Peter Eisentraut wrote:
> - The appearance of the DEB_PYTHON_PRIVATE_MODULES_DIRS variable seems
> to be unrelated to this change. I don't doubt it might be useful, but
> I just want to be sure where it's coming from.
Well, it's kind of unrelated since the old dh_python can
25 matches
Mail list logo
