summaryrefslogtreecommitdiff
path: root/docs/internals/contributing/writing-code
diff options
context:
space:
mode:
Diffstat (limited to 'docs/internals/contributing/writing-code')
-rw-r--r--docs/internals/contributing/writing-code/coding-style.txt8
1 files changed, 7 insertions, 1 deletions
diff --git a/docs/internals/contributing/writing-code/coding-style.txt b/docs/internals/contributing/writing-code/coding-style.txt
index 1f8be33e05..2fa0233e3d 100644
--- a/docs/internals/contributing/writing-code/coding-style.txt
+++ b/docs/internals/contributing/writing-code/coding-style.txt
@@ -1,5 +1,5 @@
============
-Coding Style
+Coding style
============
Please follow these coding standards when writing code for inclusion in Django.
@@ -13,6 +13,12 @@ Python style
area, but remember that :pep:`8` is only a guide, so respect the style of
the surrounding code as a primary goal.
+ One big exception to :pep:`8` is our preference of longer line lengths.
+ We're well into the 21st Century, and we have high-resolution computer
+ screens that can fit way more than 79 characters on a screen. Don't limit
+ lines of code to 79 characters if it means the code looks significantly
+ uglier or is harder to read.
+
* Use four spaces for indentation.
* Use underscores, not camelCase, for variable, function and method names