Author: adrian Date: 2012-02-17 12:03:40 -0800 (Fri, 17 Feb 2012) New Revision: 17539
Modified: django/trunk/docs/internals/contributing/writing-code/coding-style.txt Log: Added note to coding-style.txt about how we should NOT be religious about line lengths. Modified: django/trunk/docs/internals/contributing/writing-code/coding-style.txt =================================================================== --- django/trunk/docs/internals/contributing/writing-code/coding-style.txt 2012-02-17 16:51:22 UTC (rev 17538) +++ django/trunk/docs/internals/contributing/writing-code/coding-style.txt 2012-02-17 20:03:40 UTC (rev 17539) @@ -1,5 +1,5 @@ ============ -Coding Style +Coding style ============ Please follow these coding standards when writing code for inclusion in Django. @@ -13,6 +13,12 @@ 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 -- You received this message because you are subscribed to the Google Groups "Django updates" group. To post to this group, send email to django-updates@googlegroups.com. To unsubscribe from this group, send email to django-updates+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-updates?hl=en.
