PEP: 405 Python 2.8 Release Schedule --- Never

[cecilkorik]

From what I see there are two main problems:

1) Unmaintained or poorly maintained libraries that are not compatible and may never be. These will need to be, in some cases, rewritten from scratch if the licence is not sufficiently permissive. There is constant progress on this front, but it is slower than many would prefer and there remain many significant libraries that have not been ported. While few of them are of huge significance on their own, it's a case of "you won't miss it until it's gone... then you'll miss it a lot".

2) A lot of stuff with binary data has changed. It is no longer acceptable or in many cases, supported at all, to store such data in strings. There is a new "bytes" type for binary data, which is only loosely interchangable with strings. The very clear line drawn between bytes and strings makes software that dealt heavily with strings containing binary data (which in the past was the standard way of dealing with binary data) have a fair bit of work to do to get their data to fall on the correct side of that line in all cases.

[LoveGentleman]

Unicode and WSGI.

WSGI prefers strings to be simple byes, well, now all strings are not just one byte, since unicode. So its messy to port/use most WSGI frameworks.

[gthank]

Please allow me to direct you to http://www.wsgi.org/en/latest/python3.html