3 ms·
Realistically, any practical argument for Python's lack of block scope is probably just sour grapes. The real reason, I'm guessing, is that it started out as a
by mumblemumble 6y ago
Realistically, any practical argument for Python's lack of block scope is probably just sour grapes. The real reason, I'm guessing, is that it started out as a hobby project 30+ years ago, and that block scope is not something GvR personally felt was worth the effort to implement at the time.
Followed by three decades of not wanting to do that particular breaking change, because doing so would be far more painful than anything that happened in Python 3.0.
- otabdeveloper4 6y ago> ...because doing so would be far more painful than anything that happened in Python 3.0 Is this really true? I don't think lack of block scope is ever used for anything but causing bugs.
- sep_field 6y agoCould do it the same way JS did it, with const and let keywords. Breaks nothing.