I lintered my code until all the complaints went away :D
(thanks for mentioning flake8, @michaelhoffman)
cc @o_guest @talyarkoni
-
-
Woo-hoo! So much more readable now!
2 replies 0 retweets 2 likes -
Thank you for the tips!! I first tried pylint but it was nitpicky about somethings, flake8 seems more reasonable
1 reply 0 retweets 1 like -
Yeah, I've found the same. You don't want to ignore warnings. Producing too many spurious warnings causes that.
1 reply 0 retweets 1 like -
I think the main one was pylint doesn't like short variable names, but I don't think I want longer var names for (r,g,b)
1 reply 0 retweets 1 like -
Nice one!
2 replies 0 retweets 0 likes -
Sorry if you have answered this already somewhere but what is the 'dev_NUMBER' prefix? [I'm curious.]
1 reply 0 retweets 0 likes -
It's just really just 'poor' version control. Are my rough 'development' notebooks where I pilot code and keep some useful test snippets.
1 reply 0 retweets 1 like -
I want to easily go back to earlier checkpoints and not need to use git to see old vers, so I 'save as'. I do the same thing with Word docs.
1 reply 0 retweets 1 like
Ah, fair enough. As long as you don't do the same with Word documents/binary files on git, you'll make it such a pain to d/l for yourself.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.