Gosh, would it really be that difficult? There’s a command line switch to highlight incompatibilities. You wouldn’t have to go over every line by hand. To quote from the python website: docs.python.org/3.0/whatsnew/3.0.html
Besides, I think a backwards-incompatible version of Panda is a good opportunity to fix all the design flaws that were only visible in hindsight. Haven’t we heard drwr complain about some of those? Sure it would still be a lot of work, but its not like we have a deadline to meet.
Wow, sorry for the (very very) late answer, and I arrived to the same conclusion… I didnt know about the backport, it’ll can be usefull when the time will come… what i found interesting with the multiprocessing was that we could exceed the one memory module cap of python (maybe there is another way but if this is the case, I don’t know it… ).
Even if regarding what you said I seriously doubt now this module will be really usefull to me, i’ll give it a try.
And, like 90% of the code I need is python 3.0 and 2.5 (yeah, I like to be mostly up to date ) compatible, I don’t really mind it, except for the other languages translations, far more convenient with the 3.0 version.
But whatever, thanxs to you and Pro-soft for the answering and giving the link, with the time I came to think it wasn’t so a big deal to stay in 2.5.x few years longer (yeah, I still hope Disney’s targeted computers will change, and it will… but when…)
Within the past week Ubuntu Jaunty upgraded to Python 2.6 as the default. That was a fun few days of upgrades with random chunks of the system crashing =p. Starting with Ubuntu 9.04 there will probably need to be dual releases for python 2.5 and 2.6. I’ll see if I can get a package together for us crazy mofos who live on the bleeding edge.
Its not 2.6 I am worrying about, its 3.x which is giving me head aches… This new revision is just changing a LOT in the way the Python devs have to code - away from “intuitive coding” to “coding how its meant to be by the devs”.
Actually “intuitive coding” was the one and only reason why I landed here.
However, thats rumors. I never used 3.x till now.
What I meant: I hope that 2.x-releases of python are supported for a LONG time as long as its compatible with older Python code (which will break in 3.0 at least but should not in 2.6?)
Well I am not exactly a Python pro, but from all what I read, hear or see of Python 3K I don’ think that’s true. Except for the print() thing I guess most people here can still use their code. There’s also some change in range and/or xrange, that might effect people, but I am not even sure about that one.
I think the biggest problem is with the C API, not with the Python code.
And people do need to do big rewrites of Python code. “print” is just a mere example - has_key another.
It will take weeks to rewrite Panda for Python 3 - and I don’t think it’s worth it. Most other libraries and engines didn’t upgrade to Python 3 yet either. Python 2 is still supported and only hobbyists use Py3K yet.