4 ms·

Considering minor releases happen every 8 months or so (i.e., Django 1.6 will be released latter half of this year), I'm thinking that'll be enough time to work

by clicks 14y ago

Considering minor releases happen every 8 months or so (i.e., Django 1.6 will be released latter half of this year), I'm thinking that'll be enough time to work out the kinks for running Django on Python 3. I do want to point out that it was only last year people used to say that Django was _the_ thing holding everyone going from Python 2 -> Python 3. And now Django has made the move, -- others (Flask, etc.) have not.

rednukleus 14y ago
Thanks, that was the answer I was looking for.
huxley 14y ago
Django 1.6 wouldn't be a minor release, 1.x are major versions. You're more likely to see an alpha release of 1.6 in 8 months, the final released versions of Django have a roughly annual release schedule: * Django 1.4 came out March 23, 2012 * Django 1.3 came out March 23, 2011 * Django 1.2 came out May 17, 2010 * Django 1.1 came out July 29, 2009 * Django 1.0 released September 3, 2008 Update: Didn't read the part of Jacob Kaplan-Moss' response above where he says 1.6 could be coming in "6-9 months" and as in as little as 3 months. To which I'd say "Wow"
- deleted 14y ago
  [deleted]
  - huxley 14y ago
    Well, dang, I stand corrected. As a Django user, I've always understood Django 1.x to follow the Apple convention with OS X numbering. To the credit of the core team, every minor release has felt like a major improvement to me.
    - takluyver 14y ago
      Many projects roughly follow 'semantic versioning'. You change the first number for a release that breaks backwards compatibility, the second number for a feature release, and the third number for a bugfix release.
- jacobian 14y ago
  Well... 3 months is possible, but unlikely. 6-9 is more likely. 12 months is unlikely, but more likely than 3.
dtwwtd 14y ago
Tornado has supported Python 3 since mid-2011. http://www.tornadoweb.org/documentation/releases/v2.0.0.html http://www.tornadoweb.org/documentation/releases/v2.0.0.html

by clicks 14y ago

rednukleus 14y ago

Thanks, that was the answer I was looking for.

huxley 14y ago

Django 1.6 wouldn't be a minor release, 1.x are major versions. You're more likely to see an alpha release of 1.6 in 8 months, the final released versions of Django have a roughly annual release schedule: * Django 1.4 came out March 23, 2012 * Django 1.3 came out March 23, 2011 * Django 1.2 came out May 17, 2010 * Django 1.1 came out July 29, 2009 * Django 1.0 released September 3, 2008 Update: Didn't read the part of Jacob Kaplan-Moss' response above where he says 1.6 could be coming in "6-9 months" and as in as little as 3 months. To which I'd say "Wow"

deleted 14y ago
[deleted]
- huxley 14y ago
  Well, dang, I stand corrected. As a Django user, I've always understood Django 1.x to follow the Apple convention with OS X numbering. To the credit of the core team, every minor release has felt like a major improvement to me.
  - takluyver 14y ago
    Many projects roughly follow 'semantic versioning'. You change the first number for a release that breaks backwards compatibility, the second number for a feature release, and the third number for a bugfix release.
jacobian 14y ago
Well... 3 months is possible, but unlikely. 6-9 is more likely. 12 months is unlikely, but more likely than 3.

dtwwtd 14y ago

Tornado has supported Python 3 since mid-2011. http://www.tornadoweb.org/documentation/releases/v2.0.0.html http://www.tornadoweb.org/documentation/releases/v2.0.0.html