On 2020-02-11, Chris Angelico <ros...@gmail.com> wrote: > On Tue, Feb 11, 2020 at 10:01 PM Jon Ribbens via Python-list ><email@example.com> wrote: >> So while it's been about 6 years since anyone should have been >> starting any new projects using Python 2, there are plenty of >> projects that are older than that and still need supporting, >> and often it'd take some pretty huge unavoidable requirement >> to motivate a port to Python 3. > > Or just the recognition that, eventually, technical debt has to be > paid. I didn't say that everything has to stop supporting Py2 > instantly now that it's 2020, but that it's time to stop going to > great lengths for it. Py2 is a legacy system and has been for a long > time now, and if it takes a lot of effort to keep maintaining it, then > it's time to consider porting to Py3. Just how much work are you going > to do, to avoid the work of porting?
Not doing something generally doesn't involve any work. Occasionally there's a very small amount of work when something that would have been trivial in Python 3 is slightly harder in Python 2 - this thread for example, where it appears to involve one extra line of code. -- https://mail.python.org/mailman/listinfo/python-list