Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upEnable more linting #292
Enable more linting #292
Conversation
In general, <3. Thanks for doing this! I'm pretty sure I'd rather not have some of the changes because I disagree with the lint, but I think that's a small number of the changes; will have a close look through tomorrow. FWIW, there was some vague intent to just get rid of |
No worries. Im just waking up, so I'll focus on cleaning up only the actual provable user-facing bugs herein until I hear more from you. |
|
||
import urllib.request | ||
import urllib.error | ||
import urllib.parse | ||
import urllib.robotparser | ||
import md5 |
I split off the CI and pylint changes to be #293. |
@jayvdb We've landed a bunch of changes, but I'm a little fuzzy on whether all the important things in this PR have been covered now or not. Are there outstanding things we want in this PR or can we close it out? |
Quite a few parts are now simpler, but still heaps to do. I rebased and revised this last week, but was waiting for the other PRs to be merged, and was doing Google Code-in launch prep. |
I want to get 1.0.0 out, so I'm going to drop this from the milestone. Thank you for working on it! We can definitely land this in the future. |
At this point in time, I'd suggest just running Black and let it decide on the style choices. |
@hugovk Let's try and minimise the number of open PRs when we do that (i.e., wait till after we've merged many of the currently open PRs), given it'll cause conflicts with everything, but yes, applying black seems sane. (Keeping this open in lieu of opening a new issue because I'm about to go to bed |
WIP-ish PR. Interested to see if there are any parts that are objectionable.
I'm happy to split it into smaller chunks for different types of lint issues, with nice commit messages.
Also, I can add more fine tuning by implementing my own flake8-putty, which allows rules to be disabled per-file and even per-line without modifying the source, so new rules can be enforced for new code while existing lint errors in old code are ignored.
This change is