Spaces are the preferred indentation method. My_list = result = some_function_that_takes_arguments ( 'a', 'b', 'c', 'd', 'e', 'f', ) Tabs or Spaces? Indent the following should be considered there should be noĪrguments on the first line and further indentation should be used toĬlearly distinguish itself as a continuation line: Using Python’s implicit line joining inside parentheses, brackets andīraces, or using a hanging indent. Python that don’t support the feature recommended by the style guide.Ĭontinuation lines should align wrapped elements either vertically

When the code needs to remain compatible with older versions of.

Guideline and there is no other reason to be modifying that code.

Because the code in question predates the introduction of the.

To be consistent with surrounding code that also breaks it (maybeįor historic reasons) – although this is also an opportunity toĬlean up someone else’s mess (in true XP style).

When applying the guideline would make the code less readable, evenįor someone who is used to reading code that follows this PEP.

Some other good reasons to ignore a particular guideline: In particular: do not break backwards compatibility just to comply with Look at other examples and decide what looks best. However, know when to be inconsistent – sometimes style guide Consistency within a project is more important.Ĭonsistency within one module or function is the most important. As PEP 20 says, “Readability counts”.Ī style guide is about consistency. The readability of code and make it consistent across the wide The guidelines provided here are intended to improve One of Guido’s key insights is that code is read much more often than A Foolish Consistency is the Hobgoblin of Little Minds In the event of anyĬonflicts, such project-specific guides take precedence for that project. Many projects have their own coding style guidelines. Identified and past conventions are rendered obsolete by changes in This style guide evolves over time as additional conventions are Guido’s original Python Style Guide essay, with some additions from This document and PEP 257 (Docstring Conventions) were adapted from

Please see theĬompanion informational PEP describing style guidelines for the C code The standard library in the main Python distribution.

This document gives coding conventions for the Python code comprising Whitespace in Expressions and Statements.Should a Line Break Before or After a Binary Operator?.

A Foolish Consistency is the Hobgoblin of Little Minds.

Nick Coghlan Status : Active Type : Process Created : 0 Post-History : 0, 0 Toggle light / dark / auto colour theme PEP 8 – Style Guide for Python Code Author : Guido van Rossum , PEP 8 – Style Guide for Python Code | Following system colour scheme Selected dark colour scheme Selected light colour scheme Python Enhancement Proposals

Conditional inline r