Python developers won’t let go of Python 2 (www.infoworld.com)

submitted 1 year ago by ruffsl@programming.dev to c/python@programming.dev

43 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] JigglySackles@lemmy.world 5 points 1 year ago

I don't do enough for it to matter, what's wrong with 3?

[-] agressivelyPassive@feddit.de 8 points 1 year ago

It's different enough.

There are huge python 2 codebases that can't easily be ported to python 3.

[-] Vamanos@lemmy.world 7 points 1 year ago

Meh. I’ve ported a fair many py2 projects to 3. At this point just bite the bullet. Even from a security standpoint. Trying to not let my bias seep through - but it’s been so long.

[-] agressivelyPassive@feddit.de 15 points 1 year ago

Ever worked on a giant corporate codebase? I'm not saying you're wrong, but corporate internals often work counter to common sense or sanity. You'll have a giant mess of code, that would require months of work to port. The longer you wait, the more expensive it will get, but if you just wait long enough, it might not be the current manager's problem anymore. So it will be postponed and postponed.

I've seen this in real life a few times. EOL driven development. You just wait until it's absolutely impossible not to upgrade, then you hastily stop everything, do the porting in a marathon of sadness that basically rewrites everything, and if you're done, you can wait for the next EOL.

[-] Vamanos@lemmy.world 6 points 1 year ago* (last edited 1 year ago)

20 years on giant enterprise codebases. And any enterprise worth their salt at this point will be scanning these servers and flagging eosl software.

My experience the last five years of the 20 - security and service life trumps all fucking complaints about complexity.

To the point where it’s the opposite and I’m fielding weekly questions about why we’re still running an older 3.7.9 version. Among 50 other things.

[-] agressivelyPassive@feddit.de 3 points 1 year ago

Yet, there are enough companies that simply don't care. Yes, that's bad, but it's also reality.

[-] luckystarr@feddit.de 5 points 1 year ago

The trick is to assign someone the responsibility of the upgrade and give them the authority to tell the other developers how their newly added code shall look like. This will get you there eventually.

Seen it work on a >1 million SLOC project.

[-] bane_killgrind@kbin.social 7 points 1 year ago

Yeah but that requires good planning and better team structure.

That's low margin and therefore doesn't happen often enough.

[-] agressivelyPassive@feddit.de 1 points 1 year ago

This will get you there eventually.

Only if you can actually upgrade piece by piece. In a monolith, you often enough can't just upgrade new lines/methods. In those cases, it's halt all development, pull everyone into upgrading and then continue.