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

Python

6229 readers
85 users here now

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

📅 Events

October 2023

November 2023

PastJuly 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
73
Python developers won’t let go of Python 2 (www.infoworld.com)
submitted 11 months 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
[–] luckystarr@feddit.de 5 points 11 months ago (2 children)

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 11 months 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 11 months 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.