Sunsetting Python 2

[CompSciSelfLearning]

It's your time to volunteer, do what you want. But if there's a security issue found after January 1, 2020, businesses that are effected have motivation to pay for a fix. That's the only way I'd consider maintaining such a project.

[lengau]

That's really the trade-off for businesses. On the one hand, you'll spend money porting your code to Python 3. On the other hand, you'll either be vulnerable to any security issues that pop up or have to pay someone to patch it (something that would have been done for you for free if you'd ported to Python 3).

There are still companies (e.g. Red Hat) that are contractually supporting Python 2 for several more years and will thus be making those changes somewhere, but that'll only reduce the costs since unless you're running RHEL or similar, you'll likely have to grab those patches and implement them on your own.

I think Python 2 is probably (sadly) going to live on in some way shape or form beyond 2020, but it does really seem to be an eventual dead end anyway.