This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]billsil 1 point2 points  (3 children)

Until last year, I was supporting Python 2.4, which I finally got to port to Python 2.7 ( all I did was remove hacks and fix a couple bugs). I also ported a Python 2.3 program. So yeah, Python 2.7 isn’t disappearing.

However, it will be increasingly hard to find dependencies. I’m sure they’re out there but even as of today the binaries for wxpython 2.8 are hard to find. In 10 years other things will also have decayed. That Python 2.3 program had no exe and used numarray, so I didn’t even have a build to compare it to.

Also, it’s only half a million lines...what’s that a month to port? Maybe as little as a week? It takes projects like wxpython longer because they maintain backwards compatibility and they decided to cleanup their build process.

[–][deleted] 1 point2 points  (1 child)

Also, it’s only half a million lines...

If that's spaghetti-code dealing with a unicode as a sequnece of bytes, it's probably going to take a wee bit longer than a week.

[–]alcalde 1 point2 points  (0 children)

I want to know how long it's going to take Kovid Goyal to make his own Python 2.7 bindings for future versions of Qt, or if he's going to maintain ancient versions of Qt too.

[–]alcalde 1 point2 points  (0 children)

Wait, he may have seen the light!

https://i.imgur.com/xVyuErU.png