On Tue, Jun 19, 2001 at 08:35:08AM -0700, Joseph Carter wrote: > > Also, we should consider when we will move python2-* to python-*; > > AFAICR, python 1.5 -> 2.0 is a pretty simple conversion in most cases. > The biggest thing I remember is some implicit tupling you could do in 1.5 > that 2.0 refuses to tollerate. Most python written in recent history has > been written with 2.0 in mind regardless of the GPL issues since people > who use python had figured the new stuff would get into a GPL compatible > python one way or another. I suspect therefore that the number of things > which break under 2.0 should be small. That's good to hear. I don't use Python much myself, so I wouldn't know. The only reason I mentioned this is because I was the first to do so. > > I would recommend finding out what doesn't work with 2.0 first and then > trying to figure out what does or doesn't need fixing. If there isn't > much, file bugs, set a deadline, and just switch. Of course if there is a > lot, the forced march approach obviously won't work. I don't expect many > problems though and if I'm right the deadline's probably the best way - if > there's one thing consistant around here, it's procrastination. =) I like this idea and second it, assuming you're right about the first paragraph above. - Jimmy Kaplowitz jimmy@debian.org
Attachment:
pgpdsSLn2Jkgd.pgp
Description: PGP signature