Closed SPlanzer closed 3 years ago
This issue has been automatically marked as stale as there has not been any activity for sometime. The issue will be closed in 14 days if no further activity.
FYI @billgeo As discussed at this weeks planning session - A pylint report for the gazetter application.
As mentioned this is a large piece of work. The report confirms this. Pylint is requesting 4217 changes to be made.
Below (contained in the collapsible section) is a very small subsection of the report. The entire report is very large.
entire report attached
Some of these issues such as white space violation will be automatically fixed by Black. The majority will not
Thanks @SPlanzer. Is this with the default pylint rules or some rules excluded? Just wondering if we can ignore some of this to make it more manageable.
Don't know what we should/shouldn't ignore though. Any thoughts on that? @SPlanzer @strk ?
Thanks @SPlanzer. Is this with the default pylint rules or some rules excluded?
No Pylint exclusions provided when generating the report.
Don't know what we should/shouldn't ignore though. Any thoughts on that? @SPlanzer @strk ?
A few things at a quick glance: C0103: invalid-name: ~700 of these. (example: Module name "FormUtils" doesn't conform to snake_case naming style (invalid-name) C0111: Missing method docstring: - ~340 C0326: No space allowed before bracket ~1500 (will be fixed by Black) C0303: Trailing whitespace (trailing-whitespace): ` 170 (will be fixed by Black) C0301: Line too long : ~70 (mostly fixed by Black)
I do not think it is worth changing any of these at this stage but what Black will handle
I do not think there is value of a major formatting overhaul. This will do more harm than good as it is an opportunity to introduce new bugs. The source code does not follow PyLint but existing formatting is consistent and clear.
Thanks @SPlanzer. Maybe we can leave this until later then. Especially snake case. Not sure about docstrings though. Any thoughts on that @strk ?
Also, when you say
will be fixed by pylint
do you mean 'fixed by Black'?
do you mean 'fixed by Black'?
Yeah sorry Black
I have edit original to ensure that it is clearer.
I don't have opinions on formatting standards, other than please keep it readable...
War on format is waste of time so if a single format can be ensured to be maintained by a tool I'm happy to go there, only big reformatting makes it harder to spot who last touched a line of source code (most lines would be touch by formatter) - luckly git blame
as an option to ignore commits, so if such reformatting work is done in a single commit it should make things easier.
Specifically on which format to pick I really don't have an opinion, anything works for me
Okay, thanks. If it already follows some kind of consistent standard, but not pylint. Let's put this on the backlog for now.
To large to apply retrospectively
GitHub actions should test all pull requests to ensure pylint standards are meet.