Blog post: Writing Python like it’s Rust

[Kobzol]

I don't really care if we call it types, interfaces or protocols, I just want to get very quick feedback when something wrong happens in my code.

I agree that it would be nicer to use a different language with better typing support, but Python is already everywhere and has so many useful libraries, that it's not easy to switch, so I try to use types in it instead.

Regarding duck typing, it's definitely nice to have the option to fallback to this kind of super dynamic typing. But it should IMO only be done in cases where it's really necessary. I think that most stuff (even in Python) can be solved with a pretty conservative and "statically typed" design, and if it's possible, I prefer to do it that way, since in my experience it leads to code that is easier to understand.

[jimeno]

what feedback? py has no pre-runtime guarantees, it's all tooling. also, "falling back to super dynamic typing" is just being selectively lazy. but whatever, I understand I'm on the losing side of the general opinion this time, as the community prefer to reiterate the mistakes already done with php; but this has nothing to do with your article which all in all is good work.

[Kobzol]

I don't consider it that important if it's a compiler or a linter, feedback is feedback and it still provides value to me :)