@gentoobro @waltercool @sun @genmaicha @newt @ageha Then what you cobbled together in python breaks because the people who make it had to change the open socket function for some retarded purity spiral reason that in practice achieves nothing but change for the sake of change.

The snmp library (or some other library) has also changed overnight, and now your code is an incompatible mess of hard to decipher lambda functions you wrote two years ago with a syntax that only makes sense to the person who designed it and online you can't find examples on how the new version work, just examples for the old one.

I have been hostage of that bullshit language for 10 years and I regret the day I learned that garbage, no thank you.

To prevent that continuous breakage I developed my own framework with tons of exceptions so v2 and v3 code could live and switch depending on the runtime, I ended rewriting a lot of the "batteries included" to prevent breakages. I'm not a developer I can't quickly make changes to large script codebases I wrote years ago, I need to solve problems fast and can't spend a week finding out why something that worked on RHEL 8 doesn't now out of the sudden on RHEL 9. If I write a tool for a task is because I depend on it, python people do not get that, they simply don't.

Until I thought... if I rewrite all of this in C it will never break again and will run on anything. I'm glad I did python is only good for trivial stuff. Turns out not having trinkets in the language (C is spartan in comparison) makes for much simpler to understand code in the long term, and nothing fancy languages do can't be reproduced in C if you have a bit of imagination, in the end the memory of a process is flat, all code is assembler and GCC fucking rules.