Re: Python 2.0.1; transition plans for woody

2001-06-25 Thread Bruce Sass
On Mon, 25 Jun 2001, Gregor Hoffleit wrote: > On Mon, Jun 25, 2001 at 05:37:36PM +0200, Radovan Garabik wrote: > > I agree, but... why not wait until python 2.1.1 is released? > > (or, if we just discuss things a bit, it will be > > released before any action is taken and we can jump right > > to i

Re: Python 2.0.1; transition plans for woody

2001-06-25 Thread Harry Henry Gebel
On Mon, Jun 25, 2001 at 04:02:05PM -0400, Harry Henry Gebel wrote: > On Mon, Jun 25, 2001 at 04:36:28PM +0200, Gregor Hoffleit wrote: > > I vote to change over, the sooner the better. That was me not Gregor, sorry about that. -- Harry Henry Gebel West Dover Hundred, Delaware GPG encrypted email

Re: Python 2.0.1; transition plans for woody

2001-06-25 Thread Harry Henry Gebel
On Mon, Jun 25, 2001 at 04:36:28PM +0200, Gregor Hoffleit wrote: I vote to change over, the sooner the better. -- Harry Henry Gebel West Dover Hundred, Delaware GPG encrypted email gladly accepted. Key ID: B853FFFE Fingerprint: 15A6 F58D AEED 5680 B41A 61FE 5A5F BB51 B853 FFFE pgp4n18tJ6f9G.p

Re: Python 2.0.1; transition plans for woody

2001-06-25 Thread Radovan Garabik
On Mon, Jun 25, 2001 at 05:50:01PM +0200, Gregor Hoffleit wrote: > On Mon, Jun 25, 2001 at 05:42:30PM +0200, Radovan Garabik wrote: > > > > > > > well, some time ago I symlinked some modules from python1.5 to python2.0 > > (binary ones) and surprisingly they worked (python just printed warning >

Re: Python 2.0.1; transition plans for woody

2001-06-25 Thread Matthias Klose
Gregor Hoffleit writes: > On Mon, Jun 25, 2001 at 05:37:36PM +0200, Radovan Garabik wrote: > > I agree, but... why not wait until python 2.1.1 is released? > > (or, if we just discuss things a bit, it will be > > released before any action is taken and we can jump right > > to it :-)) sure, t

Re: Python 2.0.1; transition plans for woody

2001-06-25 Thread Neil Schemenauer
Gregor Hoffleit wrote: > IMHO this is the point where we should make a big step, and enforce a quick > transition of the archive to Python 2.0.1. Yes please. Packages named python suck. I'm willing to work on rebuilding packages or whatever else needs to be done. Neil

Re: Python 2.0.1; transition plans for woody

2001-06-25 Thread Mikael Hedin
Please go ahead! The fewer nameX type packages the better. Should be no problems for plucker (=me) /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 fi

Re: Python 2.0.1; transition plans for woody

2001-06-25 Thread Gregor Hoffleit
On Mon, Jun 25, 2001 at 05:42:30PM +0200, Radovan Garabik wrote: > On Mon, Jun 25, 2001 at 05:21:39PM +0200, Gregor Hoffleit wrote: > > > > With the default setup, stuff in /usr/lib/python1.5/site-packages would be > > ignored by 2.0.1. In order to make the transition easier, we might decide > > t

Re: Python 2.0.1; transition plans for woody

2001-06-25 Thread Gregor Hoffleit
On Mon, Jun 25, 2001 at 05:37:36PM +0200, Radovan Garabik wrote: > I agree, but... why not wait until python 2.1.1 is released? > (or, if we just discuss things a bit, it will be > released before any action is taken and we can jump right > to it :-)) > > You still need to modify packages when goi

Re: Python 2.0.1; transition plans for woody

2001-06-25 Thread Radovan Garabik
On Mon, Jun 25, 2001 at 05:21:39PM +0200, Gregor Hoffleit wrote: > > With the default setup, stuff in /usr/lib/python1.5/site-packages would be > ignored by 2.0.1. In order to make the transition easier, we might decide to > append /usr/lib/python1.5/site-packages to the sys.path, though: > > Alm

Re: Python 2.0.1; transition plans for woody

2001-06-25 Thread Radovan Garabik
On Mon, Jun 25, 2001 at 04:36:28PM +0200, Gregor Hoffleit wrote: > Hi, ... > > This would mean that I upload new versions of the Python packages: > > (1) python2 (python2-base etc.) would be removed > > (2) python 2.0.1-1 (python-base etc.) would replace python 1.5.2-16 > > (3) A new set

Re: Python 2.0.1; transition plans for woody

2001-06-25 Thread Gregor Hoffleit
On Tue, Jun 26, 2001 at 12:47:28AM +1000, Anthony Towns wrote: > On Mon, Jun 25, 2001 at 04:36:28PM +0200, Gregor Hoffleit wrote: > > This would mean that I upload new versions of the Python packages: > > (1) python2 (python2-base etc.) would be removed > > (2) python 2.0.1-1 (python-base etc.)

Re: Python 2.0.1; transition plans for woody

2001-06-25 Thread Federico Di Gregorio
On 26 Jun 2001 00:47:28 +1000, Anthony Towns wrote: [snip] > If you can make upgrades work; if you can not break too many > people's testing or unstable systems; and if you can get everything > rewritten/rebuilt relatively quickly, I'd say it's worth doing. err.. em.. unstable systems are there to

Re: Python 2.0.1; transition plans for woody

2001-06-25 Thread Anthony Towns
On Mon, Jun 25, 2001 at 04:36:28PM +0200, Gregor Hoffleit wrote: > This would mean that I upload new versions of the Python packages: > (1) python2 (python2-base etc.) would be removed > (2) python 2.0.1-1 (python-base etc.) would replace python 1.5.2-16 > (3) A new set of legacy packages pyt

Re: Python 2.0.1; transition plans for woody

2001-06-25 Thread Federico Di Gregorio
On 25 Jun 2001 16:36:28 +0200, Gregor Hoffleit wrote: [tech stuff snipped] > Still I think it is much preferable to make this transition before the > release of woody; when we release woody with python2-* packages this will be > a big unnecessary burden for the next release; when we make the migrat

Re: Python 2.0.1; transition plans for woody

2001-06-25 Thread Joseph Carter
On Mon, Jun 25, 2001 at 04:36:28PM +0200, Gregor Hoffleit wrote: > (3) A new set of legacy packages python15 (python152 ???) for those who > think that they depend on the old version 1.5.2. I wouldn't even bother with that, if everything C needs recompiling anyway, just recompile for 2.0 o

Python 2.0.1; transition plans for woody

2001-06-25 Thread Gregor Hoffleit
Hi, Python 2.0.1 is out, finally with a GPL compatible license. Zope 2.3.3 works fine with Python 2.0; I'm not aware of any problems with Debian packages wrt. Python 2.x. That nullifies all reasons for the existance of dual Python packages in Debian (cf. /usr/share/doc/python2/README.why-python2)