summaryrefslogtreecommitdiff
path: root/README.Coding
diff options
context:
space:
mode:
authorDouglas Bagnall <douglas.bagnall@catalyst.net.nz>2018-03-23 15:09:57 +1300
committerAndrew Bartlett <abartlet@samba.org>2018-03-23 07:28:24 +0100
commitcd1136f39bba306419ef19c2c0884e694a59f2d0 (patch)
treedd185935241f3e53ba00b6bb76c08e1223926f53 /README.Coding
parent0844c5aa22c60404044b4e6dfa51ec301194cb2a (diff)
downloadsamba-cd1136f39bba306419ef19c2c0884e694a59f2d0.tar.gz
README.Coding: mention compatible Python versions
Signed-off-by: Douglas Bagnall <douglas.bagnall@catalyst.net.nz> Reviewed-by: Andrew Bartlett <abartlet@samba.org>
Diffstat (limited to 'README.Coding')
-rw-r--r--README.Coding6
1 files changed, 3 insertions, 3 deletions
diff --git a/README.Coding b/README.Coding
index 054cf3f1079..fc807ef0f7b 100644
--- a/README.Coding
+++ b/README.Coding
@@ -22,9 +22,9 @@ closely matches what most Samba developers use already anyways, with a few
exceptions as mentioned below.
The coding style for Python code is documented in PEP8,
-http://www.python.org/pep/pep8 (with spaces).
-If you have ever worked on another free software Python project, you are
-probably already familiar with it.
+http://www.python.org/pep/pep8. New Python code should be compatible with
+Python 2.6, 2.7, and Python 3.4 onwards. This means using Python 3 syntax
+with the appropriate 'from __future__' imports.
But to save you the trouble of reading the Linux kernel style guide, here
are the highlights.