The whole Python 2 / Python 3 incompatibility issue was one of several reasons why I decided to focus on learning Ruby and Rails instead.
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.
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?
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