Merge branch 'jk/python-styles'
* jk/python-styles: CodingGuidelines: add Python coding guidelines
This commit is contained in:
@ -179,6 +179,20 @@ For C programs:
|
|||||||
- Use Git's gettext wrappers to make the user interface
|
- Use Git's gettext wrappers to make the user interface
|
||||||
translatable. See "Marking strings for translation" in po/README.
|
translatable. See "Marking strings for translation" in po/README.
|
||||||
|
|
||||||
|
For Python scripts:
|
||||||
|
|
||||||
|
- We follow PEP-8 (http://www.python.org/dev/peps/pep-0008/).
|
||||||
|
|
||||||
|
- As a minimum, we aim to be compatible with Python 2.6 and 2.7.
|
||||||
|
|
||||||
|
- Where required libraries do not restrict us to Python 2, we try to
|
||||||
|
also be compatible with Python 3.1 and later.
|
||||||
|
|
||||||
|
- When you must differentiate between Unicode literals and byte string
|
||||||
|
literals, it is OK to use the 'b' prefix. Even though the Python
|
||||||
|
documentation for version 2.6 does not mention this prefix, it has
|
||||||
|
been supported since version 2.6.0.
|
||||||
|
|
||||||
Writing Documentation:
|
Writing Documentation:
|
||||||
|
|
||||||
Every user-visible change should be reflected in the documentation.
|
Every user-visible change should be reflected in the documentation.
|
||||||
|
Reference in New Issue
Block a user