pep8

I'm trying to keep my source code under the 80 character guideline width that PEP8 recommends, but can't figure out how to wrap my doctest which has results longer than 80 characters. A noddy example: def long_string(): """ Returns a string which is wider than the recommended PEP8 linewidth >>> print long_string() 0123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789 """ return '0123456789' * 10 I've tried a couple of combinations, including using # doctest: +NORMALIZE_WHITESPACE and trying to simply wrap the line with a newline. Just figured out:

This is is just a curiosity with historical purposes: I was wondering if someone knows why the very widely used (and core module) logging doesn't follow the Python's PEP-8 naming convention . For instance, in >>> import logging >>> log = logging.getLogger("hello") I would expect it to be get_logger , but it isn't. When it comes to function names , the PEP8 standard says: mixedCase is allowed only in contexts where that's already the prevailing style (e.g. threading.py), to retain backwards compatibility. Was that the case? If so, with what other logging thingy it had to maintain backwards

I have read there are three ways for coding multi-line imports in python With slashes: from Tkinter import Tk, Frame, Button, Entry, Canvas, Text, \ LEFT, DISABLED, NORMAL, RIDGE, END Duplicating senteces: from Tkinter import Tk, Frame, Button, Entry, Canvas, Text from Tkinter import LEFT, DISABLED, NORMAL, RIDGE, END With parenthesis: from Tkinter import (Tk, Frame, Button, Entry, Canvas, Text, LEFT, DISABLED, NORMAL, RIDGE, END) Is there a recomended format or a more elegant way for this statements? Personally I go with parentheses when importing more than one component and sort them

This question already has an answer here: What is the naming convention in Python for variable and function names? 13 answers So which is better and why? def my_function(): or def myFunction(): aayoubi 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. PEP 8 advises the first form for readability. You can find it here . Function names should be lowercase, with words separated by underscores as necessary to improve readability. Harish

PEP8 E712 requires that "comparison to True should be if cond is True: or if cond: ". But if I follow this PEP8 I get different/wrong results. Why? In [1]: from pylab import * In [2]: a = array([True, True, False]) In [3]: where(a == True) Out[3]: (array([0, 1]),) # correct results with PEP violation In [4]: where(a is True) Out[4]: (array([], dtype=int64),) # wrong results without PEP violation In [5]: where(a) Out[5]: (array([0, 1]),) # correct results without PEP violation, but not as clear as the first two imho. "Where what?" That advice only applies to if statements testing for the