-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Request: Don't show PEP8 errors for tables of data #9955
Comments
Thanks for reporting. You'll be able to select what pep8 message you want to see/hide in Spyder 4. |
Will it just block all of a particular error though? Because they are useful everywhere else except tables of data |
Yes
This should be probably implemented on the linter side and not on spyder. |
@goanpeca I asked pycodestyle and they said it's downstream's responsibility. :/ |
@goanpeca, how do you think we could address this one? Probably with a regex that detects nested lists of data? |
Not sure how we can handle this :-| |
Issue Report Checklist
conda update spyder
(orpip
, if not using Anaconda)jupyter qtconsole
(if console-related)spyder --reset
Problem Description
Spyder with "Real-time code style analysis" turned on shows code style errors for tables of numbers that are formatted in a neat, readable way:
which encourages re-formatting them in a less readable way (which is contrary to the intent of PEP8):
These examples are from SciPy, for example. I asked if this exception could be added to the pycodestyle/pep8 library itself, but they will not add it. They say to use
flake8
instead and modify its rules. It would be nice if something like this could be done in Spyder.What steps reproduce the problem?
What is the expected output? What do you see instead?
It shows code style problems for code that is more-readable, and does not show them for code that is less readable.
Versions
Dependencies
The text was updated successfully, but these errors were encountered: