News for hackers. Stuff that matters.
Re:Python past, present, and future with Guido van Rossum [a... by greyman on Thursday February 23, 2017 @02:17AM (#13712252)
But didn't Guido say that everything what could be backported was already backported?

> There are a small handful of backwards incompatibilities introduced by Tauthon.

How to understand this?

Anyway, something like this was expected to happen. I wonder if it wouldn't be better if Guido would not halt python 2 development and just let it evolve.

Re:Python past, present, and future with Guido van Rossum [a... by mkesper on Thursday February 23, 2017 @05:09AM (#13712808)
This discussion goes now on since Python 3 was released. Python 2 will not be supported or developed after 2020.
Re:Python past, present, and future with Guido van Rossum [a... by greyman on Thursday February 23, 2017 @06:39AM (#13713130)
Yes, I know. The question is if this decision is correct, given that apparently a lot of people and companies just doesn't plan to switch no matter what.
Re:Python past, present, and future with Guido van Rossum [a... by StavrosK on Thursday February 23, 2017 @06:51AM (#13713174)
Well, if you want people to switch to 3, you do need to apply some pressure by end-of-lifing 2.
Re:Python past, present, and future with Guido van Rossum [a... by dagw on Thursday February 23, 2017 @06:53AM (#13713184)
Or you could offer something in 3 which will make switching enticing enough for people to do so of their own free will.
Re:Python past, present, and future with Guido van Rossum [a... by shakna on Thursday February 23, 2017 @07:41AM (#13713404)
Proper unicode handling, list comprehensions, generators, await & async, TSL 1.1 & 1.2 support, better namespace handling, better string interpolation, and better argument parsing are just a few of the things that you get.

Is there a feature that could entice these people? Or have they made up their minds?

Re:Python past, present, and future with Guido van Rossum [a... by dagw on Thursday February 23, 2017 @07:54AM (#13713458)
List (and set,dict and generator) comprehensions and generators are available in python2. Await & async and unicode handling are nice improvements, but you could do both in python2 well enough if it was important to you. TSL support I don't use in python so I cannot comment on it. And I've honestly never found namespace handling or string interpolation a problem.

Is there a feature that could entice these people? Or have they made up their minds?

A working, stable, version of http://pyparallel.org/ would entice the hell out of me.

Re:Python past, present, and future with Guido van Rossum [a... by lmm on Thursday February 23, 2017 @08:47AM (#13713780)
It's not practical to safely work with non-ASCII strings in Python 2. There are too many "arbitrarily mangle my string" functions available (both in the language proper and in libraries), and the only way to avoid them is constant vigilance, which doesn't scale.
Re:Python past, present, and future with Guido van Rossum [a... by dorkygator on Thursday February 23, 2017 @04:26AM (#13712668)
He left the door open for the community to continue work on Python 2. It looks like somebody took up that offer.
Re:Python past, present, and future with Guido van Rossum [a... by greyman on Thursday February 23, 2017 @06:39AM (#13713126)
Yes and no. Community can continue, but only under different name. So only fork is allowed.