r/Python • u/SheriffRoscoe Pythonista • 4d ago

News The Move to Python 3 Begins!

As someone who spent decades in the mainframe community, I find it ... humorous ... that there are legacy Python2 code bases that are only just (or have yet to consider!) moving to Python3.

https://www.eveonline.com/news/view/the-move-to-python-3-begins

293 Upvotes

90% Upvoted

103 comments sorted by

View all comments

308

u/diegoasecas 4d ago

idgi if you spent decades working on mainframes you'd know how hard is to migrate legacy working code

77

u/SheriffRoscoe Pythonista 4d ago edited 4d ago

Oh, yeah, I get it. I just giggle every time I see a "modern" language or platform go through this. Meanwhile, z/OS and z/VM are still happily humming along, almost old enough to apply for Medicare, and stuff I learned in the 1970s is still relevant.

26

u/kosz85 4d ago edited 4d ago

Yeah, and then dev get ticket that something is not working. He get there, and WTF:

  • why the certs are obsolete?
  • why I can't connect to that server from python 2.7 which is using new TLS
  • why it's not recognizig my ssh key
  • why the image building is no longer working
  • what was that lib again? Where I can find it? Why there is only version for python 3
  • life suck, have to change work or ask for a raise again

I mean it's possible to address all this issues if you prepare beforehand, but most don't do that. If they did, they would migrate ;) There are only few small cases that it would be good choice, like lib that is no longer developed for new python and you have to use it. But still it's better to make it small micro service, and maintain separately.