pep8

There is probably an easy answer for this, just not sure how to tease it out of my searches. I adhere to PEP8 in my python code, and I'm currently using OptionParser for a script I'm writing. To prevent lines from going beyond a with of 80, I use the backslash where needed. For example: if __name__=='__main__': usage = '%prog [options]\nWithout any options, will display 10 random \ users of each type.' parser = OptionParser(usage) That indent after the backslash results in: ~$ ./er_usersearch -h Usage: er_usersearch [options] Without any options, will display 10 random users of each type. That

Given this Python class, implementing a Django form, how would you properly break this to meet the PEP8 standards? class MyForm(forms.Form): categories = forms.CharField(required=False, widget=forms.SelectMultiple(choices=CATEGORY_VALUE), label="Categories") additional_item_ship_cost = forms.CharField(required=False, max_length=10, label="Additional Item Ship Cost") Specifically, the widget= and label= parameters violate the PEP8 rules for line length. What comes to mind immediately is that I could define the widget and label outside of the class and then use them in the class definition, but

I want to use pep8 as my makeprg in order to check and fix my code compliance to PEP8 (Style guide for python code) . I used the command :set makeprg=pep8\ --repeat\ % , and when I do :make it works, the error list is populated and I can use :cn , :cp and :copen to navigate and see the error list in the QuickFix window. But as soon as I change something in my python source file the errorlist becomes empty, the QuickFix window loses its content and I cannot navigate the list anymore. I suspect that this is caused by PyFlakes, a Vim extension that highlights Python errors on-the-fly. How can I

I ran into unexpected results in a python if clause today: import numpy if numpy.allclose(6.0, 6.1, rtol=0, atol=0.5): print 'close enough' # works as expected (prints message) if numpy.allclose(6.0, 6.1, rtol=0, atol=0.5) is True: print 'close enough' # does NOT work as expected (prints nothing) After some poking around (i.e., this question , and in particular this answer ), I understand the cause: the type returned by numpy.allclose() is numpy.bool_ rather than plain old bool , and apparently if foo = numpy.bool_(1) , then if foo will evaluate to True while if foo is True will evaluate to

Consider the following code: def add_function(a, b): c = str(a) + b print "c is %s" % c def add_int_function(c, d): e = c + d print "the vaule of e is %d" % e if __name__ =="__main__": add_function(59906, 'kugrt5') add_int_function(1, 2) It always shows me: "expected 2 blank lines ，found 1" in a add_int_function , but not in the add_function . When I add two spaces in front of the def add_int_function(c, d): there is a error shows unindent does not match any outer indentation level in the end of add_function : Just add another line between your function definitions : 1 line : 2 lines: This is

I got a list of functions that may fail, and if one fail, I don't want the script to stop, but to continue with next function. I am executing it with something like this : list_of_functions = [f_a,f_b,f_c] for current_function in list_of_functions: try: current_function() except Exception: print(traceback.format_exc()) It's working fine, but it is not PEP8 compliant: When catching exceptions, mention specific exceptions whenever possible instead of using a bare except: clause. For example, use: try: import platform_specific_module except ImportError: platform_specific_module = None A bare