-
-
Notifications
You must be signed in to change notification settings - Fork 449
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
Flycheck doesn't return casing errors for Python #1544
Comments
Thanks for the report. Can you show an input file, and the command line output of the tools? |
Sure! File: https://github.com/billywade/yendor/blob/master/yendor/gui/npc.py Output:
|
Thanks, this is helpful. Can you see what happens if you select just the python-pylint checker (with |
Okay, so doing that returns the appropriate response. Thanks! It looks like all of the casing errors are all referred to as info-level errors. Is this something I should take up with |
Possibly :) |
Alright! I'ma call this a Marc thing until I'm told otherwise. |
What you did, and what you expected to happen instead
I have pycheckers set up with pylint, pep8, flake8, pyflakes, mypy2, and mypy3. When I run either pylint or flake8 independently, it will return all of the casing issues I have. However, Flycheck doesn't output any of these issues.
Whether and how you were able to [reproduce the issue in emacs -Q][emacsQ]
I couldn't get flycheck to run at all in Q, but that's most likely user error.
Your Flycheck setup from
M-x flycheck-verify-setup
Your operating system
Manjaro Linux, 64-bit, recently updated.
Your Emacs version from
M-x emacs-version
GNU Emacs 26.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.22.30) of 2018-07-05
Your Flycheck version from
M-x flycheck-version
Flycheck version: 32snapshot (package: 20190213.1525)
Thanks!
The text was updated successfully, but these errors were encountered: