Removing Python 2.x support from Django for version 2.0

Post by ma2rten » Thu, Jan 19, 2017, 3:58 PM UTC

joeyspn wrote: post #119

stevehiehn wrote: post #10

Good. I've been getting into python a bit because i have an interest in datascience. I'm mostly a Java dev. I have to say the python2/3 divide is a real turn off. Many of the science libs want to use seem to be in 2.7 with no signs of moving.

> Many of the science libs want to use seem to be in 2.7 with no signs of moving The most important scientific libraries have pledged to drop support before 2020, and are all python3-ready http://www.python3statement.org/

Post by Chris2048 » Thu, Jan 19, 2017, 4:00 PM UTC

scrollaway wrote: post #229

Chris2048 wrote: post #226

Earlier quoted context omitted.

Which comments are you interpreting as demands? >> A lack of being paid (money at least) doesn't imply no obligations, nor freedom from criticism. > Excellent, then you should be fine with me criticizing the attitude that's been displayed here. Great. Do you actually have a response to this point in context, then? > This is the same as the IE6 situation: Want support for it? Pay extra for it! You did not argue this.…

You're appropriating criticism that was not directed to you, but to coldtea. Here and elsewhere. Edit: Yes, appropriating . You're taking criticism I specifically directed at coldtea, applying them to your comments and then complaining it doesn't fit. I am done talking to you. Edit 2: This was not meant to sound as aggressive as it did, sorry.

Post by dagmx » Thu, Jan 19, 2017, 4:01 PM UTC

coldtea wrote: post #31

Flimm wrote: post #5

The next release, Django 1.11, will be a long-term support release, and the one after that, Django 2.0, will no longer support Python 2. https://www.djangoproject.com/weblog/2015/jun/25/roadmap/ I've grow to highly respect the Django project for its good documentation, its healthy consideration for backwards compatibility, security, steady improvements and all round goodness.

> its healthy consideration for backwards compatibility Like screwing the huge majority of users with Python 2.x Django projects and having them update or be left behind?

Post by linsomniac » Thu, Jan 19, 2017, 4:02 PM UTC

ergo14 wrote: post #126

danpalmer wrote: post #40

Earlier quoted context omitted.

I'd prefer to hold judgement on the internals of Django, however as a developer using the API, I also think it's a pleasure to use. There is a very high level of consistency, similar patterns used throughout, and the architecture results in a project structure that I can explain to a new developer who has never used Django before in minutes. I find few frameworks really scale in terms of structure and consistency, an…

I would bet my horse on https://trypyramid.com/ when it comes to API consistency, I've updated my applications from 0.9 to 1.7 and that was a breeze. Over the years it was exceptionally great experience.

Post by metaphorm » Thu, Jan 19, 2017, 4:08 PM UTC

IndianAstronaut wrote: post #192

yuvadam wrote: post #6

This call has been made a while back, and it makes perfect sense. Python 2 is slowly being EOL'd and if you're starting a brand new Django project there's no reason on earth you should choose Python 2 anymore. Sure legacy projects still need support and for that they get the 1.11 LTS, but otherwise it's really time to move on.

>Python 2 is slowly being EOL'd and if you're starting a brand new Django project there's no reason on earth you should choose Python 2 anymore. Except that there are still some critical packages that aren't on Python 3 yet. Not to mention a lot of functionality breaks even if the libraries do exist, which means you have to code things up quite differently sometimes.