Raphael Hertzog writes:
On Tue, 13 Jun 2006, Marc Dequènes wrote:
Coin,
[...]
You can find the current class here :
http://perso.duckcorp.org/duck/soya-new-policy/
Some things to fix:
cdbs_python_build_versions := $(patsubst python%, %, $(shell pyversions -r
debian/control |
Marc Dequènes wrote:
As you may have heard, Python packaging is moving fast these days. We
plan the move the current Python version to 2.4 and in the same time
are drafting a new policy and creating new tools to greatly improve
the current situation. All this leads to the need for a newer
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
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 into
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 when
* 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
--
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
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/
Maybe I'm
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 why
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 the same in
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-users
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
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 modules and
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 and
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. :-)
-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,
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
17 matches
Mail list logo
