7 ms·

Is Django 1.5 finally going to support Python 3? Python 3's been out for what, 5 years now, and the major web framework for the language still doesn't support i

by kyllo 14y ago

Is Django 1.5 finally going to support Python 3? Python 3's been out for what, 5 years now, and the major web framework for the language still doesn't support it yet? The whole Python 2 / Python 3 incompatibility issue was one of several reasons why I decided to focus on learning Ruby and Rails instead.

meric 14y ago
Yes, but the app ecosystem not so much.
makaimc 14y ago
Yes, Django 1.5 supports Python 3 although the authors recommend waiting until 1.6 for production sites (https://www.djangoproject.com/weblog/2012/aug/19/experimental-python-3-support/ https://www.djangoproject.com/weblog/2012/aug/19/experimenta...). The larger question is whether the libraries you want to use support Python 3. Common libraries such as django-debug-toolbar unfortunately do not yet support 3 (https://python3wos.appspot.com/ https://python3wos.appspot.com/).
keypusher 14y ago
To be fair, very few projects from the Python ecosystem have been eager to jump to Python 3.
lawnchair_larry 14y ago
The whole Python 2 / Python 3 incompatibility issue was one of several reasons why I decided to focus on learning Ruby and Rails instead. Although I understand that mentality and share it on some level, that was a bad way to make that decision. If you write Python 2.7 and avoid things marked deprecated, you are nearly compatible with Python 3 by default. Besides, this one isn't Django's fault.
FireBeyond 14y ago
"The whole Python 2 / Python 3 incompatibility issue was one of several reasons why I decided to focus on learning Ruby and Rails instead." Confused. It seems, and I'm happy to be corrected, that many new Rails versions deprecate, often with little notice, even core components. Or am I wrong?
- Buzaga 14y ago
  Yes this happens. But the point is that Rails and its community like to stay on the edge, if something deprecates you fix and it's done... the thought of framework developers trying too hard to be compatible with everyone's apps, people backporting language features to an older version so they don't have to switch and a popular framework dragging the evolution of a language is much more worrisome to a lot of developers I'm not entitled to talk about Django but that's my perception... There was a really funny comment in a thread like this back then that impersonated Rails saying "New Ruby version? let's deprecate everything!" and Django going "On the weekend we're gonna discuss making Django compatible with the 5 year old Python" And then someone said "What I like about this comment is that it pisses off both sides of the table" :p

by kyllo 14y ago

meric 14y ago

Yes, but the app ecosystem not so much.

makaimc 14y ago

Yes, Django 1.5 supports Python 3 although the authors recommend waiting until 1.6 for production sites (https://www.djangoproject.com/weblog/2012/aug/19/experimental-python-3-support/ https://www.djangoproject.com/weblog/2012/aug/19/experimenta...). The larger question is whether the libraries you want to use support Python 3. Common libraries such as django-debug-toolbar unfortunately do not yet support 3 (https://python3wos.appspot.com/ https://python3wos.appspot.com/).

keypusher 14y ago

To be fair, very few projects from the Python ecosystem have been eager to jump to Python 3.

lawnchair_larry 14y ago

The whole Python 2 / Python 3 incompatibility issue was one of several reasons why I decided to focus on learning Ruby and Rails instead. Although I understand that mentality and share it on some level, that was a bad way to make that decision. If you write Python 2.7 and avoid things marked deprecated, you are nearly compatible with Python 3 by default. Besides, this one isn't Django's fault.

FireBeyond 14y ago

"The whole Python 2 / Python 3 incompatibility issue was one of several reasons why I decided to focus on learning Ruby and Rails instead." Confused. It seems, and I'm happy to be corrected, that many new Rails versions deprecate, often with little notice, even core components. Or am I wrong?

Buzaga 14y ago
Yes this happens. But the point is that Rails and its community like to stay on the edge, if something deprecates you fix and it's done... the thought of framework developers trying too hard to be compatible with everyone's apps, people backporting language features to an older version so they don't have to switch and a popular framework dragging the evolution of a language is much more worrisome to a lot of developers I'm not entitled to talk about Django but that's my perception... There was a really funny comment in a thread like this back then that impersonated Rails saying "New Ruby version? let's deprecate everything!" and Django going "On the weekend we're gonna discuss making Django compatible with the 5 year old Python" And then someone said "What I like about this comment is that it pisses off both sides of the table" :p