3 ms·
lol, no. > typing is not pythonic, at all. Calling something unpythonic is a best practice. Typing vastly reduces the amount of low gain tests. It helps navi
by sitkack 5y ago
lol, no.
> typing is not pythonic, at all.
Calling something unpythonic is a best practice.
Typing vastly reduces the amount of low gain tests. It helps navigate the code and catch errors before they hit production. If you don't want types, don't use them.
> They require additional knowledge to implement correct type hints.
That is the point. Maybe PHP with semantic white space is your style.
- wheelerof4te 5y agoCalling something unpythonic is a way of keeping the spirit of Python. We use that magic word to ward off terrible demons, and prevent them from defiling our beloved language. "Typing vastly reduces the amount of low gain tests. It helps navigate the code and catch errors before they hit production." It also makes you too reliant on your IDE to guide you through. I think much more clearly when I'm in a text editor that forces me to slowly consider every statement that I write. Bonus points, I'm not bogged down with typing boilerplate, which is almost required if your IDE is to be useful at all.
- sitkack 5y agoCasting spells on others in unpythonic.
- wheelerof4te 5y agoNot if they're Cleric spells :)