[Info-vax] Python 2 support ends 1-Jan-2020

[Arne Vajhøj]

On 1/4/2019 10:24 AM, Stephen Hoffman wrote:
> On 2019-01-04 02:25:51 +0000, Dave Froble said:
>> Sounds like an interesting predicament.  Maybe this could be a preview 
>> for Steve's ideas breaking things in order to move on.  Somebody keep 
>> track of this.
> 
> The Python 3 division change—switching from an integer result to a 
> floating point result—has been underway for most of twenty years.
> 
> Python source code migration tools and testing tools have been available 
> for a long while too, with a tool that allows Python 3 code to also 
> operate on Python 2, and another that allows migrating Python 2 code 
> forward to Python 3.
> 
> https://docs.python.org/3/howto/pyporting.html

It has been known for a long time. And tools exist.

But that does not mean everybody is going to move to 3.

I suspect that those that use Python for their primary applications
will have started the migration process and will complete.

But primary applications are a relative small part of the Python world.

And I just don't see all the supporting applications in Python being
migrated.

It is work no matter how many guides and tools. It does not add revenue
or reduce cost. The business risk of not migration may be considered
acceptable because it is only supporting applications.

My guess is that Python will still be used in 2030.

> And yes, there'll be Python 2 source code around for decades.  There are 
> still VAX systems around, and there'll remain a hopefully-decreasing 
> apps and code that uses $crelog and ODS-2 and DECnet and telnet, too. 

:-)

Arne