Skip to content

DOC: Remove mypy from pre commit #35066

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 1, 2020
Merged

DOC: Remove mypy from pre commit #35066

merged 1 commit into from
Sep 1, 2020

Conversation

erfannariman
Copy link
Member

Copy link
Member

@WillAyd WillAyd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@jreback
Copy link
Contributor

jreback commented Jul 2, 2020

are we sure we really want to do this? whats going to happen is that mypy issues will just happen on the CI, which is much later in the process.

@WillAyd
Copy link
Member

WillAyd commented Jul 2, 2020

I don't have a strong point of view but the current usage of mypy is very limited in scope and can in a lot of cases yield a different result than CI anyway. I do think a full mypy run pre-push would be a good compromise instead of a partial run every commit just not sure how feasible that is

@gfyoung gfyoung added the Docs label Jul 3, 2020
@MarcoGorelli MarcoGorelli added Code Style Code style, linting, code_checks Typing type annotations, mypy/pyright type checking and removed Docs labels Jul 4, 2020
@erfannariman
Copy link
Member Author

This issue is still a thing and for now I solve this with --no-verify at commit, which is not desirable either, since it will skip the other tests as well. Can we maybe add the "needs discussion" tag to have some other opinions as well? @jreback @WillAyd

Just for my understanding, we can't solve the error messages which are occuring now? That would be the most desirable solution right?

@jbrockmendel
Copy link
Member

we can't solve the error messages which are occuring now?

cc @simonjayhawkins could this be resolved by ensuring that we have the same version of mypy run locally as on the CI?

@simonjayhawkins
Copy link
Member

we can't solve the error messages which are occuring now?

cc @simonjayhawkins could this be resolved by ensuring that we have the same version of mypy run locally as on the CI?

AFAIK mypy runs fine locally with mypy 0.730 (although with other packages adding types e.g. pytest, probably need to make sure local environment matches environment on ci). for ci the dev enviroment is used. i.e. environment.yaml

as far as the pre commit is concerned, I'm on Windows and didn't seem to work out of the box and not spent any time looking any further.

@erfannariman
Copy link
Member Author

@simonjayhawkins I saw that there were some changes concerning mypy, is PR still relevant?

@simonjayhawkins
Copy link
Member

@simonjayhawkins I saw that there were some changes concerning mypy, is PR still relevant?

I'm not really aware of the issues here, as I don't use pre commit, so I'm not the right person to ask/comment.

@TomAugspurger
Copy link
Contributor

Let's just remove it. We can try again once it's more mature.

@TomAugspurger TomAugspurger merged commit 08bcea6 into pandas-dev:master Sep 1, 2020
kesmit13 pushed a commit to kesmit13/pandas that referenced this pull request Nov 2, 2020
@twoertwein twoertwein mentioned this pull request Sep 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Code Style Code style, linting, code_checks Typing type annotations, mypy/pyright type checking
Projects
None yet
Development

Successfully merging this pull request may close these issues.

DOC: Contributor guideline should guide contributors for expected local mypy failures
8 participants