Skip to content

--use-python-path is an attractive nuisance #1411

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

Closed
gvanrossum opened this issue Apr 20, 2016 · 2 comments
Closed

--use-python-path is an attractive nuisance #1411

gvanrossum opened this issue Apr 20, 2016 · 2 comments

Comments

@gvanrossum
Copy link
Member

It seems that many people try to use --use-python-path because they see some missing imports (e.g. django, see #1410) and then mypy crashes on some random problem. Maybe we shouldn't have --use-python-path at all? @JukkaL, why was it introduced anyway?

@gvanrossum
Copy link
Member Author

UPDATE: I think it was introduced in response to #486 (the diff was 6230e3f by the same user). But I wish it never existed -- people are really better off ignoring imports for which no stubs exist than trying to deal with the errors and crashes from analyzing 3rd party (or stdlib) libraries that haven't been made mypy-clean.

@JukkaL
Copy link
Collaborator

JukkaL commented Apr 20, 2016

I tend to agree that --use-python-path isn't very useful as such. If #638 was implemented (ignoring errors in library modules) and mypy hardly ever crashed, it might be useful, but currently it's unlikely to be helpful. Let's just remove it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants