3 ms·
Of course I'm not a good judge, I have been programming Python since 1.4 and my colleagues also all have Python experience. But at least I like the idea that i
by Scarblac 7y ago
Of course I'm not a good judge, I have been programming Python since 1.4 and my colleagues also all have Python experience.
But at least I like the idea that it gives an error message when confronted with ambiguity. That way it doesn't do something you didn't expect silently. Sadly it only gives it at runtime, not at compile time.
- xscott 7y agoI'm not sure what your point is about Python 1.4. Maybe it's that you're past the point where these things trip you up. However, there are plenty of cases where Python won't give an error message too. Make a typo somewhere in the middle of your function, and it'll quietly introduce a new variable instead of letting you know. A rarely used branch of an if-statement could hide this indefinitely. This could also be avoided (or at least mitigated) by requiring variables to be declared explicitly.