this post was submitted on 06 Oct 2023
73 points (95.1% liked)

Python

6337 readers
18 users here now

Welcome to the Python community on the programming.dev Lemmy instance!

📅 Events

PastNovember 2023

October 2023

July 2023

August 2023

September 2023

🐍 Python project:
💓 Python Community:
✨ Python Ecosystem:
🌌 Fediverse
Communities
Projects
Feeds

founded 1 year ago
MODERATORS
erlingur@programming.dev
jnovinger@programming.dev
norambna@programming.dev
73
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
[–] Overarch3784@kbin.social 28 points 1 year ago (1 children)

I think the biggest problem would be libraries which are not available in 3.x. I just rewrote a python script some time ago and the syntax changes were pretty easy to change with search and replace.

[–] Dr_Cog@mander.xyz 6 points 1 year ago (1 children)

I don't see a problem. For one, it's been 15 years: the vast majority of libraries have been ported by now. And like you said, you can fix the syntax with basically a find/replace script, so any stragglers can be modified easily.

There really isn't any excuse to still be using Python 2 anymore

[–] Alphare@lemmy.world 5 points 1 year ago

While I agree that people should have moved on for a while, the idea that porting Python 2 to 3 only involves "find and replace" or a tool like 2to3 is only true in the most trivial cases. Anything that touches bytes, unicode, network or files to do anything remotely involved needs a lot more care. I should know, our codebase still suffers from the occasional bug due to this, even though it's been years.