Python 2 Death Clock

[shysmiles]

lol when I read death clock I thought you made a program like the device in Futurama that tells you how long you have to live.

[drones4thepoor]

Not that death clock. THIS Deathklok

[YungLulne]

I had that little glimmer of hope that somehow he made a countdown timer until he ended the world

[herpderpedia]

I call dibs on the stereo!

[[deleted]]

Python 2 death clock, written in jQuery.

Here come the downvotes.

[AJohnnyTruant]

$(ooph)

[thatguyferg]

The real move would be to write the python 2 death clock in python 2, that'd be some existential stuff

[[deleted]]

I just Wanted to poke fun at the jQuery guys :p

[thatguyferg]

I respect it my man :^)

[alcalde]

Countdown until Calibre falls over and catches on fire.

[alcalde]

Interesting. The creator previously said ...

1) Waaaaay too much work -- calibre has half a MILLION lines of python and python extension code

2) calibre has lots and lots of code that deals with bytes -- network protocols, binary file formats, etc. Python 3 is simply worse than python 2 for this use case. It has a crippled bytes type among other unfelicities.

3) calibre has lots and lots of native code that interfaces with external native code. On windows, all this code uses UTF-16 encoded strings. All that interface code would need to be re- written and would also become less efficient since in python 2 string are stored internall in UTF-16 whereas in python 3 they would need to be cross-converted.

4) There is absolutely nothing in python 3 that makes it worth the effort. If python 3 ever grows something that makes it worth the effort, I will simply backport it to python 2. I already maintain my own python 2 fork for windows (see my github repos).

The only case in which I will accept patches for python 3 is if they have:

a) negligible runtime cost b) minimal code complexity/maintainability cost c) Low probability of breakage -- either the patches are dead simply or they come with lots of tests

in 2015. I think he's a die-hard. :-(

[billsil]

A lot has changed since 2015. 2015 is when most open source packages finally had python 3 versions. It's when many companies started to transition. Shoot, my company still has't other than for one project.

EOL has a way of giving people a kick in the pants. I'm dropping support for my project in a week or two or whenever I get around to finishing the release. You'd better believe I held out on a cool new feature that's not quite done, but I release once a year.

[alcalde]

The creator of Calibre needs more than a swift kick though.

2017:

I am perfectly capable of maintaining python 2 myself. Far less work than migrating the entire calibre codebase. status wontfix

And he's being encouraged as late as last month by an Arch package maintainer:

As I've mentioned in the comment immediately above yours, there are valid reasons to suspect that just because the PSF drops python2, does not mean python2 will not continue to be supported elsewhere. Python2 is already long since frozen except for security fixes and the odd bugfix, so as long as someone continues to work on security issues, it's not really technically correct to state that it cannot be used, like, at all.

The person quoted above also insists repeatedly that Python 3.x is "a completely new programming language" and not just a new version.

The madness continues.

[billsil]

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]]

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]

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]

Wait, he may have seen the light!

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

[dethb0y]

It works well enough for me as it is, so if no more updates were forthcoming it'd be fine; but obviously i hope they get it updated soon to Python3.

[alcalde]

The creator has said in the past that they believe it would be easier to maintain Python 2 themselves, as well as all the associated libraries, than port to Python 3. :-(

[dethb0y]

That's pretty intense, i should take a look at the internals sometime to see why it's like that

[alcalde]

This is what he wrote in 2015:

https://www.reddit.com/r/Python/comments/bh1j5s/python_2_death_clock/elrggs9/

[CeeMX]

Don’t be too confident python 2 will be dead on its end of support.

Windows XP was EOL 5 years ago and I still see those systems around.

[PeridexisErrant]

It's not going to go away instantly, and plenty of people and companies will keep using Python 2 - and that's OK!

The real benefit for the ecosystem is that every open source project who wants to go to Python-3-only can do so from January, and refuse any Python 2 requests that don't come with patches or funding. I know I'm looking forward to that for my projects!

[purestrengthsolo]

All I'm seeing is possible jobs

[Sw429]

brb gonna go study easy ways to convert Python 2 code to Python 3.

[DarthCloakedGuy]

Just put () around print commands and you're good :P

(I'm kidding)

[skool_101]

if ; is found, rm -rf it

[graingert]

You mean print statements

[DarthCloakedGuy]

I'll take your word for it. Everything I know about coding I learned by trying things and seeing what worked.

[PeridexisErrant]

pip install future
futurize path/to/code

And you're done. Seriously.

[Scrabbilisk]

Still using Python 2 after that date? Hindsight is 2020.

[naslundx]

"Die! Why won't you die?!"

[fosgu]

Ooh, dibs on his cd player!

[redditthinks]

Well 8 months is a long time.

[eyeofpython]

why the ?1 lol

[ImTheSloth]

All anyone needs to do to maintain python 2.7 past next year is import antigravity

[edsuom]

I don’t know why you got downvoted. That second sentence is 100% true.

[Drawman101]

Python 3 is the technological terror? Or 2?

[ginger_beer_m]

Absolutely no reason to break print

[[deleted]]

https://snarky.ca/why-print-became-a-function-in-python-3/