this post was submitted on 04 Aug 2024
61 points (100.0% liked)

Python

6406 readers
8 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
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 3 months ago (1 children)

Oh yeah, I forgot about the distutils thing. Yeah, I had to fix that too. But at least it wasn't hours of wading through and retesting old code.

[–] FizzyOrange 2 points 3 months ago (1 children)

In fairness for the invalid escape sequence thing static linters (Pylint, Pyright, etc.) should be already telling you about it.

[–] [email protected] 2 points 3 months ago* (last edited 3 months ago) (1 children)

Yes of course. If I run pyflakes or mypy on our code, it's a complete shitshow. But that's not the point.

The point is, for better or worse, however imperfect our code is, it run cleanly and predictably in older Python interpreters. When I have to correct legacy stuff that is known to work well, I compromise hundreds of hours of formal and informal testing.

Imperfect code that has been running flawlessly for a long time and has proven its reliability is better than more perfect code that hasn't been tested as much.

In fact, in certain industries like the aero industry, it doesn't matter if you find slightly bad code after the system has been certified: it's frozen and you leave it the hell alone unless it's critical. Fortunately we're not exactly in that situation, but we do have customers who require - and pay for - configuration control, and those Python issues kind of make everything more difficult needlessly for us. Lucky for us, our Python packages are mostly support code, so it's not too critical. But we do have to be careful and thorough.

[–] FizzyOrange 1 points 3 months ago