News for hackers. Stuff that matters.
Re:Why I'm Making Python 2.8 by int_19h on Saturday December 10, 2016 @03:50PM (#13147833)
It's worth noting that Microsoft is still keeping VB6 on life support, in a sense. The tooling is not guaranteed to work on modern OSes (and there is a bunch of actual breakage, although community has found workarounds so far).

But the runtime is still supported - in fact, it ships with the OS! If you have any non-ARM version of Windows, up to and including Win10, around, check the file named msvbvm60.dll in C:\Windows\SysWOW64 - that's it ("MS VB VM").

And because it ships as an OS component, the official support policy is the same as the rest of the OS, which is at least 5 years of mainstream support (longer if there's no successor release), and then at least 5 years of extended support. This is even clarified specifically for VB6:

https://msdn.microsoft.com/en-us/vstudio/ms788708.aspx

Since VB6 was first released in 1998, this marks 18 years of continued support to date; and if it's not dropped from the OS within the next 2 years, it has a chance of hitting 30 years...

For what it's worth, PSF also has a fairly generous (especially for a non-commercial OSS project) support policy for Python 2.7 - it had already extended the end-of-life date for it once to 2020:

https://www.python.org/dev/peps/pep-0373/#id2

Re:Why I'm Making Python 2.8 by BuckRogers on Saturday December 10, 2016 @06:58PM (#13148707)
That's not generosity that's control. They kept maintaining 2.7 because they knew if they didn't someone would definitely have done exactly this.

They are only trying to run out the clock on other people's interest- an effort to kill Python2 so it doesn't evolve.