yeah, maybe. 1.4 set minimum 2.5, 1.5 set 2.6, 1.6 will (probably) be 2.7 only. 1.7 could either stick with 2.7 and 2.0 be a py3 milestone, or it could drop 2.x

yeah, maybe. 1.4 set minimum 2.5, 1.5 set 2.6, 1.6 will (probably) be 2.7 only. 1.7 could either stick with 2.7 and 2.0 be a py3 milestone, or it could drop 2.x and provide a py3-only codebase for developing 2.0. gotta check all the talks and announcements, I don't remember if it was decided yet. >until all the packages you might need for a project supports py3k I don't see it as a problem. most of them don't support py3 because django was py2.x. there is still at least a year or year and half to 1.7, it's a lot of time.