set up mypy hook for incremental adoption#199
Conversation
neersighted
left a comment
There was a problem hiding this comment.
Same as on poetry -- lets add some comments and rebase to fix the merge conflicts.
|
@neersighted this should be good to go. Not sure what's caused that python 3.10 workflow failure |
|
The mypy error is an open issue (see python/mypy#1393) and only occurs on 3.10 since
|
|
Go ahead with |
|
@neersighted do you mind triggering the CI for me? |
neersighted
left a comment
There was a problem hiding this comment.
Please note that when I say 'like in Poetry,' I really mean 'like in the linked PR' that I am working to get merged.
|
i've aligned the pre-commit config with the |
|
Looks like we get a failure on pypy, which is interesting. Is this rebased onto the latest master? |
it is now |
|
|
rebased on master again. let's see if that helps |
I think the better thing to do here is to not depend on mypy in Alternatively, we could add a marker to only install on CPython (see the black dep above) -- but I'm thinking we should just remove the black and isort deps in the future and rely on pre-commit as the main poetry repo does. |
i've removed the mypy dep for now. |
as per the comment here - python-poetry/poetry#4510
as per the comment here - python-poetry/poetry#4510
as per the comment here - python-poetry/poetry#4510
for some reason i had to use different config to successfully exclude the
_vendordirectory