Re: Question about python policy
On Wed, 2004-02-11 at 02:14, Graham Wilson wrote: I think I'll do this for python-albatross as well. It'll be a really tiny package but at least it'll fix the issue of not being able to install both python 2.2 and 2.3 versions. Does it make sense to have both versions installed? Why might someone want to do that? The only situation that comes to mind is supporting applications written in an older dialect of python (ie. 2.2 vs. 2.3 and similar transitions in the future). While 2.2 code should run flawlessly on 2.3, there are some semantic differences (for example the introduction in 2.3 of the boolean type) that could cause unexpected behaviour. Therefore, having the option of keeping your old software running with python 2.2 while porting it to 2.3 (or writing a 2.3-based replacement) can be important to someone. And then there's the case of because we can. :) -- Fabian Fagerholm [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part
Re: Question about python policy
Fabian Fagerholm [EMAIL PROTECTED] wrote: Hello all, Hi, Firstly, it seems a little silly to duplicate all the code in both packages. I guess there's really no other way of doing it, since there There used to be a tool called python-central (look in the mailing list archives) that allowed packages to ship pure-python modules *once* under /usr/lib/python/site-packages/ and have them automatically byte-compiled for the various pythonX.Y installed (through Debian packages, of course, your custom Python in /usr/local was not affected). It was said that it would integrate the main python packages after the initial proof of concept and testing period, but I never saw that happen. I don't know why. -- Florent
