Much of the value of PEP-8 is to stop people arguing about inconsequential formatting rules, and get on with writing good, consistently formatted code. Sure, no one really thinks that 79 is optimal, but there’s no obvious gain in changing it to 99 or 119 or whatever your preferred line length is. I think the … Read more
If we consult the documentation on flake 8 we see: Anti-pattern Note: Despite being in the anti-pattern section, this will soon be considered the best practice. income = (gross_wages + taxable_interest) Best practice Note: Despite being in the best practice section, this will soon be considered an anti-pattern. income = (gross_wages + taxable_interest) So the … Read more
[x for x in (1,2,3) ] works fine, so you can pretty much do as you please. I’d personally prefer [something_that_is_pretty_long for something_that_is_pretty_long in somethings_that_are_pretty_long] The reason why \ isn’t appreciated very much is that it appears at the end of a line, where it either doesn’t stand out or needs extra padding, which has … Read more
You can use autopep8! Whilst you make yourself a cup of coffee this tool happily removes all those pesky PEP8 violations which don’t change the meaning of the code. Install it via pip: pip install autopep8 Apply this to a specific file: autopep8 py_file –in-place or to your project (recursively), the verbose option gives you … Read more
Well, I am a bit curious, so I just tested the three myself right after asking the question 😉 Ok, this is not a very serious review, but here is what I can say: I tried the tools with the default settings (it’s important because you can pretty much choose your check rules) on the … Read more
Adding # noqa to a line indicates that the linter (a program that automatically checks code quality) should not check this line. Any warnings that code may have generated will be ignored. That line may have something that “looks bad” to the linter, but the developer understands and intends it to be there for some … Read more
Since neighboring string constants are automatically concatenated, you can code it like this: s = (“this is my really, really, really, really, really, really, ” “really long string that I’d like to shorten.”) Note no plus sign, and I added the extra comma and space that follows the formatting of your example. Personally I don’t … Read more
You could use additional parentheses: subkeyword = ( Session.query(Subkeyword.subkeyword_id, Subkeyword.subkeyword_word) .filter_by(subkeyword_company_id=self.e_company_id) .filter_by(subkeyword_word=subkeyword_word) .filter_by(subkeyword_active=True) .one() )
There’s no performance difference, as they compile to the same bytecode: >>> import dis >>> dis.dis(“not x is None”) 1 0 LOAD_NAME 0 (x) 2 LOAD_CONST 0 (None) 4 COMPARE_OP 9 (is not) 6 RETURN_VALUE >>> dis.dis(“x is not None”) 1 0 LOAD_NAME 0 (x) 2 LOAD_CONST 0 (None) 4 COMPARE_OP 9 (is not) 6 … Read more
Well well, seems like everybody is strongly biased towards spaces. I use tabs exclusively. I know very well why. Tabs are actually a cool invention, that came after spaces. It allows you to indent without pushing space millions of times or using a fake tab (that produces spaces). I really don’t get why everybody is … Read more