-
Notifications
You must be signed in to change notification settings - Fork 184
The configuration files for Jupyter produce many lint errors now #410
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
Comments
The "too many #", or comment should start with I think the trailing whitespace comes from the traitlets package. (and no worries if you don't find the right package, it some dark magic) |
Thanks for taking a look at this!
Feel free to do as you like, but if it were me, I'd make them just |
I believe the point of having 2 #, is if you uncomment the whole file, it is still valid python. oh you make it just a single pound for headers, it is not the case anymore. |
I don't understand? If you uncomment |
Ha you are right. Then I guess it's to distinguish header from description. I guess we could use a different marker for header then, I'm pretty sure a decade ago it was different and made to block comment/ uncomment. |
Sounds great to me |
The generated configuration files don't adhere to the default behavior of standard linters. In particular:
#
should be followed by exactly one space (there should never be any##
).# noqa
should be marked with its rule number (in this case, F821). And,(This appears to have been changed recently.)
I'm not sure if this was the correct project, but I spent about 30 minutes searching through the various projects.
The text was updated successfully, but these errors were encountered: