The last assert would have given you a warning (SyntaxWarning: assertion is always true, perhaps remove parentheses?) if you ran it through a full interpreter, not through IDLE. Because assert is a keyword and not a function, you are actually passing in a tuple as the first argument and leaving off the second argument. Recall … Read more
Personally I go with parentheses when importing more than one component and sort them alphabetically. Like so: from Tkinter import ( Button, Canvas, DISABLED, END, Entry, Frame, LEFT, NORMAL, RIDGE, Text, Tk, ) This has the added advantage of easily seeing what components have been added / removed in each commit or PR. Overall though … Read more
This is a case where a line continuation character is preferred to open parentheses. ShortName.objects.distinct() \ .filter().values() # looks better The need for this style becomes more obvious as method names get longer and as methods start taking arguments: return some_collection.get_objects(locator=l5) \ .get_distinct(case_insensitive=True) \ .filter(predicate=query(q5)) \ .values() PEP 8 is intend to be interpreted with … 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() )
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
Imports are generally sorted alphabetically and described in various places besides PEP 8. Alphabetically sorted modules are quicker to read and searchable. After all, Python is all about readability. Also, it is easier to verify that something is imported, and avoids duplicate imports. There is nothing available in PEP 8 regarding sorting. So it’s all … 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
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
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
for everything related to Python’s style guide: i’d recommend you read PEP8. To answer your question: Function names should be lowercase, with words separated by underscores as necessary to improve readability.