News for hackers. Stuff that matters.
Re:Django's future, and Python 3 by ubernostrum on Wednesday March 14, 2012 @01:39AM (#3701974)
Er, no, we're not "waiting for the community to shift".

When Django 1.0 was released, we supported minimum Python 2.3. Dropping 2.3 and then 2.4 were major logistical hurdles; they were incredibly widely deployed, and were the stock Python for many platforms with long-term support. So it was going to take a while, no matter what, for us to sensibly deprecate those Python versions without just throwing a bunch of our users under a bus. And, of course, deprecating everything older than 2.6 is a prerequisite for starting to actually adopt 3.x.

Meanwhile, the first few releases in the Python 3 series weren't really meant for widespread adoption, ever. They were there so people could start getting a taste of Python 3 and working out a migration process while shaking out remaining issues for Python itself.

We are now at a confluence of two very happy things:

1. We've dropped our support for the older Python 2.x releases, without just screwing over a bunch of people, and by year's end we'll be a minimum-2.6 project, and

2. Python 3.2 (the current 3.x) is really quite a nice release, and Python 3.3 (later this year) looks like it'll really put the spit and polish on the Python 3.x series, meaning it's a very attractive time to be targeting Python 3.

This is the first time we've realistically been in a position to actually make the jump, and we're taking that opportunity.

Re:Django's future, and Python 3 by taybenlor on Wednesday March 14, 2012 @01:47AM (#3701992)
Fair enough, the impression I got from the above link was that Django was waiting for the community.

I'll hold back on commenting now because my insight into the Python community is limited to what I hear from friends who develop on Python. Though something I've noticed is that many of them are making the switch to Node.

Re:Django's future, and Python 3 by tbatterii on Wednesday March 14, 2012 @09:41AM (#3703113)
there wasn't even an agreed upon spec for WSGI on python 3 until last year IIRC. That needed to happen first.
Re:Django's future, and Python 3 by maaku on Wednesday March 14, 2012 @02:14PM (#3704514)
And, to be fair, as soon as the py3k WSGI spec was agreed upon the Django core developers also started implementing and pushing this transition strategy. It was a big deal at DjangoCon '11.
Re:Django's future, and Python 3 by tbatterii on Wednesday March 14, 2012 @02:30PM (#3704614)
I think every framework did. cherrypy landed there first.