TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Sunsetting Python 2 is a bit of an issue for banks like JPMorgan

6 pointsby alexis2bover 5 years ago

4 comments

protomythover 5 years ago
Well, they have the money to pay someone for support &#x2F; back-porting security patches. I wonder what system they are running Python on as Red Hat is ok for a while.<p>This actually brings an interesting question on what other languages &#x2F; systems they have used in the past and does Python represent a new lifetime concern given some of the older platforms.
gigatexalover 5 years ago
I wonder if the transition could be so hard for some large installations that they move entire codebases to a different language. I guess not, because if they could do that they’d have moved to python 3.
csenseover 5 years ago
What <i>should</i> happen here, is that banks should either pay to accelerate transition to Python 3 to meet the deadline, or they should pay to fund somebody to continue to maintain Python 2.<p>What <i>will</i> happen here, is banks won&#x27;t see any issue, because their Python 2 software still works after the sunset. It&#x27;ll be business as usual, and there will eventually be security incidents due to running Python 2.
o_nateover 5 years ago
If they only use it internally and not on external-facing sites then the security issue is somewhat less urgent.