Hi, I'm probably missing something big, but here are my thoughts: Why mess with all these versioned python? Could we not have python-base (that will be version 2.1 soon), and for the ones who need, python-base-x.y? And the python-base will be the default/newest available?
If packages install modules in .../python1.5/xxx, they have to depend on python (>=1.5, << 1.6). Any package that violates this has a serious bug, and it can be easily fixed. Packages could preferably install modules in /usr/lib/python/xxx, and the no versioned depend is needed. The python-base then has to compile all the modules in /usr/lib/python/ on an upgrade. This seems too simple, what am I missing? I think the proposed scheme with python2.1 and module2.0 et.al. is really ugly and messy. As a luser, I would be confused with all these numbers in the names of packages. There should be only python, python-this and python-that too choose from. In my opinion that is. Please enlighten me! (I maintain plucker, a small pyton package.) /Micce -- Mikael Hedin, MSc +46 (0)980 79176 Swedish Institute of Space Physics +46 (0)8 344979 (home) Box 812, S-981 28 KIRUNA, Sweden +46 (0)70 5891533 (mobile) [gpg key fingerprint = 387F A8DB DC2A 50E3 FE26 30C4 5793 29D3 C01B 2A22]
