-
-
Notifications
You must be signed in to change notification settings - Fork 16.1k
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
Need instructions about pylint/pychecker setup #674
Comments
thats looks that you are using virtualenv, but your pylint\pychecker\pep8\pyflakes\flake8 installed at system globally |
No virtualenv is used here. All of flask, flask-login, pylint, pychecker and pyflakes are installed system-wide. Pylint is started as follows:
i.e. the modules related to "cabinet" are not installed system-wide, but they import flask-related modules from the global installation. And they work when imported from the command line or from a script. |
Well, actually, module PS @patrakov: that's the output of Pylint or Pychecker? |
This is the minimal test file demonstrating the problem (save as cabinet.py):
This is the beginning of the output from pylint:
This is the output from pychecker:
|
I hit this too. There is this: http://engineering.pave.com/post/51820567994/welcome-linting-flask-ext |
I think this should be covered elsewhere. Just for the record: flask.ext.foo does not have to be used, you can use flask_foo with new extensions and flaskext.foo with old ones. The |
Any attempt to run pylint or pychecker on anything that uses any Flask extension, e.g.:
produces errors like the following:
Some documentation is needed how to coerce pylint and pychecker into understanding how flask.ext.login is imported.
The text was updated successfully, but these errors were encountered: