-
Notifications
You must be signed in to change notification settings - Fork 1
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
SQLAlchemy models not having a query() attribute #63
Comments
So maybe we need a thing just like the django thing to ignore these specific errors |
Yes, that's probably the case. This probably requires a new |
On second thought, it might be an issue with Flask. Flask extensions are imported from flask.ext.* while they actually reside in flask_*, can we somehow tell pylint to look there instead? That will resolve most of the false positives. |
It turns out someone already asked that question: https://bitbucket.org/logilab/pylint/issue/95/how-can-i-write-a-plugin-to-change-imports The answer is currently 'no' but it is being worked on. |
Doesn't look like much has happened on this. I am unable to use landscape.io with my flask projects right now. Any suggestions on workarounds?
|
Here I've the same issue. With Flask you've lots of issues due to the extensions ;-) My solution, ignore them as I test the code extensively. However, this is suboptimal, and a better solution from prospector should be used ;-) |
Same issue here too. |
I made a pylint plugin that fixes the |
@jschaf great! Now they should include it in prospector and landscape :-) |
@jschaf @teleyinex On it :) |
woot!!!!! |
In my case I'm using the Flask-SQLAlchemy package
The text was updated successfully, but these errors were encountered: