We have functional python2.6 in experimental since few days (python-support in
experimental has 2.6 in supported versions as well, BTW) and (future) 2.6
transition will require some changes (other than checking compatibility with
new Python version or building new extensions) in debian/ directory
Le mercredi 25 mars 2009 à 22:22 +0100, Piotr Ożarowski a écrit :
* python2.6 is using dist-packages instead of site-packages and it installs to
/usr/local by default:
+ add --install-layout=deb option to setup.py call in debian/rules (or
py_setup_install_args from python.mk, see
[Josselin Mouette, 2009-03-25]
* python-central is partially fixed in 0.6.10 so most of the packages don't
need preinst maintainer script
Will this work for full upgrades from lenny, in which it isn’t fixed?
I hope we'll find a way to make sure python-central will be the first
one which
Le mercredi 25 mars 2009 à 22:53 +0100, Piotr Ożarowski a écrit :
I hope we'll find a way to make sure python-central will be the first
one which will be upgraded (Pre-Depends somewhere? Backporting some
changes in Lenny's python-central?)
Making one package (e.g. python-support) conflict with
Michael Schutte mi...@uiae.at writes:
This is how I understand the problem: python-central writes to
/usr/lib/python*/site-packages, while python-support uses
/var/lib/python-support/python*. Python finds docutils/__init__.py
in one directory and doesn’t look for modules starting with
5 matches
Mail list logo
