-
Notifications
You must be signed in to change notification settings - Fork 171
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
[BUG] no way to specify some mypy args #499
Comments
Hey there @gmankab, |
This is somewhat related to #446. Would be nice to provide path to |
it`s great :) |
There are many mypy options that are not handled by Propsector, should we use generic code to handle all the to mypy options? |
I think that would make sense, I imagine it'd require finding those option values from mypy internals but a lot of prospector involves accessing private APIs. I didn't write this integration so I'm not completely sure how it works. |
OK, when I have some time I will start some deeper investigations :-) |
Describe the bug
Hello, here are some very important options in mypy linter, like
--ignore-missing-imports
and--no-site-packages
, prospector understands first one, but doesn't understand second one.To Reproduce
prospector_profile.yml
:main.py
:prospector command:
mypy command:
running mypy command without args gives two errors:
Adding first argument disables first error, and adding second argument disables second error.
But not with prospector.
If I commenting arguments for mypy in
prospector_profile.yml
:Then I getting same two errors. But if I uncommenting it, only second error disappears, while first error
Library stubs not installed for "requests"
still here.Expected behavior
More universal way to specify arguments, for example:
or:
or:
Environment:
Additional context
The text was updated successfully, but these errors were encountered: