The Python Software Foundation (a group of volunteers who look after the Python programming language) announced publicly that they will “sunset Python 2” as of 1 January 2020. From that date on, even if a security problem is found in Python 2, PSF won’t do anything about it.
There’s been plenty of warning that this was coming. Python 3 was launched 11 years ago in 2008 and the original intention was to stop supporting it in 2015. Out of the kindness of their hearts, the Python Software Foundation agreed to keep supporting the old version until 2020 in the express belief that, “that the extra 5 years is sufficient to transition off of Python 2…if not before.”
For some organizations, that extra five years does seem to have been a help. Instagram, for example, moved to Python 3 from Python 2.7 amid much fanfare in 2017 with no issues for its 400 million daily users. Dropbox did a similar migration between 2015 and 2018.
Banks, however, have been dragging their feet. One of the draggers is J.P. Morgan, which runs its all-important Athena next generation pricing, risk management, analysis and trade management platform on Python 2.7. The bank didn’t respond to a request to comment for this article, but sources said JPM is not going to be ready to switch fully to Python 3 by the 1 January deadline.
Does this matter? What happens when the PSF stops supporting its old language? Clearly, platforms like Athena will keep working. J.P. Morgan said last year that it has 2,000 developers working on Athena, and some of them are likely to be diverted to creating security patches. Equally, specialist vendors are offering to support Python 2 beyond the January deadline and banks can always pay for their services.
By the middle of next year, then, banks are likely to be some of the last places using Python 2. With most new developers learning Python 3, Python 2 expertise could be a valuable skill for a few months until if – and when – banks complete their migrations. That will surely happen one day.