mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-10-31 01:25:32 +00:00
Code Issues 32 Releases Wiki Activity

Added note to coding-style.txt about how we should NOT be religious about line lengths.

Browse Source 
git-svn-id: http://code.djangoproject.com/svn/django/trunk@17539 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Adrian Holovaty
2012-02-17 20:03:40 +00:00
parent 7ecb6813c9
commit 9fa536dc4f
1 changed files with 7 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/internals/contributing/writing-code/coding-style.txt
View File

@@ -1,5 +1,5 @@
============ ============
Coding Style Coding style
============ ============
Please follow these coding standards when writing code for inclusion in Django. 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 area, but remember that :pep:`8` is only a guide, so respect the style of
the surrounding code as a primary goal. 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 four spaces for indentation.
* Use underscores, not camelCase, for variable, function and method names * Use underscores, not camelCase, for variable, function and method names