From 9fa536dc4f1b4c815ad21a28290bc5142d339cc1 Mon Sep 17 00:00:00 2001 From: Adrian Holovaty Date: Fri, 17 Feb 2012 20:03:40 +0000 Subject: [PATCH] Added note to coding-style.txt about how we should NOT be religious about line lengths. git-svn-id: http://code.djangoproject.com/svn/django/trunk@17539 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/internals/contributing/writing-code/coding-style.txt | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/internals/contributing/writing-code/coding-style.txt b/docs/internals/contributing/writing-code/coding-style.txt index 1f8be33e05f..2fa0233e3d0 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