News for hackers. Stuff that matters.
Re:How Many Lines of C It Takes to Execute a and B in Python? by esafak on Monday December 11, 2023 @02:18PM (#38604159)
"Tech debt doesn't matter!"

"We're going to redesign it the right way after we get this version out the door!"

Re:How Many Lines of C It Takes to Execute a and B in Python? by wongarsu on Monday December 11, 2023 @03:34PM (#38605151)
Arguably those redesigns might have happened if the Python 2->3 transition hadn't received a decade of extremely vocal pushback
Re:How Many Lines of C It Takes to Execute a and B in Python? by fullspectrumdev on Monday December 11, 2023 @05:22PM (#38606280)
What’s funny is the breaking change that caused us the most headaches with 2->3 was the changes to fucking print.

I’m still finding broken print as a statement instead a function issues in codebases, somehow.

Re:How Many Lines of C It Takes to Execute a and B in Python? by pwdisswordfishc on Tuesday December 12, 2023 @09:55AM (#38612930)
It’s the easiest one to fix, though. 2to3 does it easily. If it were the only change, we would not be having this conversation. It might have even not deserved a major version bump (given that even minor releases of Python don't conserve backwards compatibility).