Skip to content
This repository has been archived by the owner on May 19, 2019. It is now read-only.

Code style

Jump to bottom
korovkinand edited this page Feb 7, 2018 · 8 revisions

Read pep8 and use it as first place style guide

These rules may add, overwrite or emphasize pep8 ones:

  • Don't put large code with multiple actions in one line. Split it into several lines in accordance with functional logic
  • Give sensible names for functions, vars and constants. Function's name should be started with verb and shortly describe what fnc do. Constants should be written using UPPER case
Clone this wiki locally