Removing Python 2.x support from Django for version 2.0

Post by nodamage » Thu, Jan 19, 2017, 9:14 PM UTC

bmh100 wrote: post #182

nodamage wrote: post #75

I have a Python 2.7 project that has been running smoothly for many years now and I'm having trouble finding a reason to upgrade to Python 3. The project uses the unicode type to represent all strings, and encodes/decodes as necessary (usually to UTF-8) when doing I/O. I haven't really had any of the Unicode handling problems that people seem to complain about in Python 2. Can someone explain what benefit I would act…

You gain access to continued language support in 2020. New features involving strings will have less risk of bugs. The "range" function is more memory efficient. Integer division automatically floors, reducing bug risk. Dictionaries with guaranteed ordering. Thousands separator in string formatting. Bit length on integers. Combinations with replacement on itertools. New, faster I/O library and faster json. Concurrent…

Post by desas » Thu, Jan 19, 2017, 9:16 PM UTC

paulddraper wrote: post #326

Joeboy wrote: post #279

Earlier quoted context omitted.

For three years, if you release your project the day the LTS comes out.

How long do you expect? Java 7 had less than four years of support. Ubuntu Desktop LTS was three years, and starting with 12.04 it increased to five years. That's a language runtime and an operation system known for their stability, forming the bottom of very wide and deep ecosystems. Show me a web framework with a 3 year LTS, and I'm overjoyed.

Post by nostrademons » Thu, Jan 19, 2017, 9:16 PM UTC

toyg wrote: post #350

nostrademons wrote: post #301

Earlier quoted context omitted.

2 years is not an unusual time between starting product development and seeing any sort of major customer uptake, and if you're in that time period, your priority really should be getting the customers rather than futzing with code migrations.

It's still the case that a bad call was made when the codebase was started, picking a language version that was already on its way out. It's like starting a new project now with Java 7 o .Net 2.0.

Post by andrewfong » Thu, Jan 19, 2017, 9:28 PM UTC

strange_quark wrote: post #304

dplgk wrote: post #282

Earlier quoted context omitted.

> They break backwards compatibility For the most part, they think they things through a lot and most importantly they document breaking changes. Their approach is an absolute dream compared to, say, updating xcode/iOS apps. It's a total shit show at Apple.

Ha, if you think that updating iOS apps is bad, try updating all your node modules to the latest version without anything breaking.

Post by urda » Thu, Jan 19, 2017, 10:14 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?