4 ms·
>I don't know how other IDEs behave, but VScode + the Python extensions try to infer the missing hints and you end up with beauties such as `str | None | Any |
by coldtea 2y ago
>I don't know how other IDEs behave, but VScode + the Python extensions try to infer the missing hints and you end up with beauties such as `str | None | Any | Unknown`, which of course are completely meaningless.
Are they correct? If they're correct (even though they are a superset of the actual intended type) then what's the problem?
At worst, it's like not having type checks for that particular package.
- deleted 2y ago[deleted]
- wenc 2y agoThey are verbose but correct. I've caught some errors this way. I usually don't think of None as a potential return value (= voids in C) but the LSP code analysis usually picks up on code paths that don't return a value. I don't find Python's typing valuable for Jupyter type explorations, but they're immensely valuable for catching little issues in production code.