Mercurial > pylearn
comparison doc/v2_planning/coding_style.txt @ 1020:53f6eb80abf1
coding_style: More links and sections to discuss
author | Olivier Delalleau <delallea@iro> |
---|---|
date | Fri, 03 Sep 2010 16:20:10 -0400 |
parents | af80b7d182af |
children | e21b3fdec4ef |
comparison
equal
deleted
inserted
replaced
1019:91916536a304 | 1020:53f6eb80abf1 |
---|---|
6 - Dumitru | 6 - Dumitru |
7 - Fred | 7 - Fred |
8 - David | 8 - David |
9 - Olivier D [leader unless David wants to be] | 9 - Olivier D [leader unless David wants to be] |
10 | 10 |
11 Existing Python coding style specifications: | 11 Existing Python coding style specifications and guidelines: |
12 -------------------------------------------- | 12 ----------------------------------------------------------- |
13 | 13 |
14 * http://www.python.org/dev/peps/pep-0008/ | 14 * http://www.python.org/dev/peps/pep-0008/ |
15 * http://google-styleguide.googlecode.com/svn/trunk/pyguide.html | 15 * http://google-styleguide.googlecode.com/svn/trunk/pyguide.html |
16 * http://www.voidspace.org.uk/python/articles/python_style_guide.shtml | |
17 * http://python.net/~goodger/projects/pycon/2007/idiomatic/handout.html | |
18 * http://www.cs.caltech.edu/courses/cs11/material/python/misc/python_style_guide.html | |
19 * http://barry.warsaw.us/software/STYLEGUIDE.txt | |
20 * http://self.maluke.com/style | |
21 * http://chandlerproject.org/Projects/ChandlerCodingStyleGuidelines | |
22 * http://lists.osafoundation.org/pipermail/dev/2003-March/000479.html | |
23 * http://learnpython.pbworks.com/PythonTricks | |
24 * http://eikke.com/how-not-to-write-python-code/ | |
25 * http://jaynes.colorado.edu/PythonGuidelines.html | |
26 * http://docs.djangoproject.com/en/dev/internals/contributing/#coding-style | |
16 | 27 |
28 We will probably want to take PEP-8 as starting point, and read what other | |
29 people think about it / how other coding guidelines differ from it. | |
30 | |
31 Documentation: | |
32 -------------- | |
33 | |
34 How do we write doc? | |
35 | |
36 Python 3: | |
37 --------- | |
38 | |
39 Is it reasonable to have coding guidelines that would make the code as | |
40 compatible as possible with Python 3? | |
41 | |
42 |