aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMartin Braun <martin.braun@ettus.com>2019-09-04 15:12:38 -0700
committerMartin Braun <martin.braun@ettus.com>2019-11-26 11:49:08 -0800
commit6c756248146c023c02b2cd96b697c21aefa9bf36 (patch)
treeb2c25154bc8529daa697a6f368784f7571b577c3
parent9b0702c546d10530af34deb7ab25391b7a7db87e (diff)
downloaduhd-6c756248146c023c02b2cd96b697c21aefa9bf36.tar.gz
uhd-6c756248146c023c02b2cd96b697c21aefa9bf36.tar.bz2
uhd-6c756248146c023c02b2cd96b697c21aefa9bf36.zip
Update CODING guidelines
- Remove reference to Python 2
-rw-r--r--CODING.md7
1 files changed, 3 insertions, 4 deletions
diff --git a/CODING.md b/CODING.md
index ebba79310..d368943bd 100644
--- a/CODING.md
+++ b/CODING.md
@@ -120,10 +120,9 @@ std::map<std::string, std::string> bar =
## Python-specific Guidelines
-* Keep Python code compatible with Py2k and Py3k. There are plenty of tools to
- aid with this, such as `futurize`.
-* Follow the suggestions in [PEP8][Pep8]
- and [PEP257][Pep257]. The former is about
+* Starting with UHD 4.0, Python 2 is no longer supported, and we don't need to
+ accommodate for it any longer. Prefer Python 3 constructs.
+* Follow the suggestions in [PEP8][Pep8] and [PEP257][Pep257]. The former is about
code layout in general, the latter about docstrings.
* Pylint is good tool for helping with following code guidelines. It's very
fussy though, so don't get too worked up about following its suggestions.