add ParserError to type stub#174
Conversation
|
Thank you. Are you able to add a CI check here for us as well? |
I can do that. I see the current pytest is done through conda and directly coding in installing dependencies in the workflow. If I create a |
I think you are more knowledgeable and defer to your judgement for what is best. |
|
Added. Im not super familiar with type stubs, but I believe these are only used to signal to downstream applications. I'm not sure that you get the benefit (and pain) of type checking the code inside this package. This is outside the scope of this PR, just wanted to point this out for consideration. Edit: even if what I said above is true, the benefit of adding the CI check for mypy is that at least the type stubs are internally consistent and valid. |
|
pinging @gamecss on this for input |
|
Sorry :) |

ParserError is missing from type stubs and it causes errors in downstream type checking. See MatthewFlamm/pynws#109.
I don't see any type checking on your CI, but it passes a mypy check when run locally.