Linked by Thom Holwerda on Thu 9th Oct 2008 21:04 UTC, submitted by ganges master
Thread beginning with comment 333047
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
2.6 is a stepping stone for the transition, and 3.0 is shaping up rather nicely.
And will be out next week or so, IIRC. I haven't RTFA'd, and it may cover that. But no one should be left thinking that 3.0 is 6 months away or anything. ;-)
3.0 fixes some niggling design issues. After 17 years, Guido and the other devs have swatted a few flies. There is no reason not to start learning with 2.6, 2.5, or 2.4. One might want to upgrade from < 2.4 before starting.
I don't think 3.0 will be adopted for a long time. So if you wish to distribute your applications, or if you do web applications (e.g. Django, Turbogears) and serve on a hosted platform, even 2.6 will be too new target.
Many distributions still only have Python 2.4.
For personal projects, sure, go ahead and use Python 3.0, it needs testing.






Member since:
2005-07-13
agreed, though i would say to anyone who plans on starting in at this point, wait for 3.0. there are some major changes to the architecute and syntax, not to mention the removal of old and unused bits. 2.6 is a stepping stone for the transition, and 3.0 is shaping up rather nicely.