Documentation/4.2/Developers/Style Guide/Python

From Slicer Wiki
Revision as of 07:37, 14 June 2013 by UpdateBot (talk | contribs) (Prepend documentation/versioncheck template. See
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Home < Documentation < 4.2 < Developers < Style Guide < Python

For the latest Slicer documentation, visit the read-the-docs.

Follow PEP 8 standards: Official PEP 8 Guidelines


  • Indentation is --- 4 spaces per level ---
    • Do not use tabs, EVER! Those who insist on using tabs for indentation will be a pariah in the community and summarily shot on sight.
  • Text encoding
    • ASCII or Latin-1 (Python 2+)
    • UTF-8 preferred, Latin-1 acceptable (Python 3)
  • Comparisons
    • To singletons (e.g. None)
      • Use 'is' or 'is not', never equality operations
    • To booleans (True, False)
      • Don't ever compare with True or False (For further explanation, see PEP 8)


  • Maximum line length is 79 characters
  • Prefix class definitions with two blank lines
  • Imports
    • Grouped in order of scope/commonallity
      1. Standard library imports
      2. Related third party imports
      3. Local apps/library specific imports
    • One package per line (with or without multiple function/module/class imports from the package)
  • Avoid extraneous whitespaces
  • Naming conventions

Checking your code

There is a handy command line tool to check your code against the PEP 8 standard called pep8. It has options to turn off specific warnings and errors in case you (almost always) have to break from the standard. You can download and install it from it's Github repo