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 > > versions at once (which is fine for me now, but maybe not everyone), or > > better, make python-whateveritscalled understand diversions of the > > target (per-version) module names. > > By diverting the directory name which is not in sys.path, you could > divert all versions at once, diverting the directory in > /usr/lib/pythonX.Y you can divert them by version. > > Ok, I think that something else, i.e. how to handle different versions > of a module. Looking at the benefits(?) of eggs ;). What about the > following setup: /usr/lib/pythonX.Y/dist-packages is added to > sys.path, python policy requires to install distribution packages into > this place, maybe supported by a distutils patch adding a new option > to setup.py. when you do build your own modules these are installed > into /usr/lib/pythonX.Y/site-packages. By changing the order of the > two directories you can priorize your locally installed modules. (yes, > we do have the /usr/local/lib/pythonX.Y/site-packages directory as > well, but making this the default would break the existing packaging). This sounds like an excellent solution. -- Joe Wreschnig <piman@debian.org>
Attachment:
signature.asc
Description: This is a digitally signed message part