Mercurial > pylearn

comparison doc/v2_planning/coding_style.txt @ 1134:0653a85ff2e8

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
coding_style: Moved url about Numpy conversion to Python 3 to the url list
author Olivier Delalleau <delallea@iro>
date Wed, 15 Sep 2010 15:38:45 -0400
parents 9baa47482ccc
children 5f0c8ff2b3b6
comparison
equal deleted inserted replaced
1133:9baa47482ccc 1134:0653a85ff2e8
143 * Official Python coding style guide: http://www.python.org/dev/peps/pep-0008 143 * Official Python coding style guide: http://www.python.org/dev/peps/pep-0008
144 * Official docstring conventions: http://www.python.org/dev/peps/pep-0257 144 * Official docstring conventions: http://www.python.org/dev/peps/pep-0257
145 * Google Python Style Guide: http://google-styleguide.googlecode.com/svn/trunk/pyguide.html 145 * Google Python Style Guide: http://google-styleguide.googlecode.com/svn/trunk/pyguide.html
146 * Interesting 146 * Interesting
147 * Code Like a Pythonista: http://python.net/~goodger/projects/pycon/2007/idiomatic/handout.html 147 * Code Like a Pythonista: http://python.net/~goodger/projects/pycon/2007/idiomatic/handout.html
148 * Numpy notes on conversion to Python 3: http://projects.scipy.org/numpy/browser/trunk/doc/Py3K.txt
148 * Can skip 149 * Can skip
149 * Python style for university class: http://www.cs.caltech.edu/courses/cs11/material/python/misc/python_style_guide.html 150 * Python style for university class: http://www.cs.caltech.edu/courses/cs11/material/python/misc/python_style_guide.html
150 * Mailman coding style: http://barry.warsaw.us/software/STYLEGUIDE.txt 151 * Mailman coding style: http://barry.warsaw.us/software/STYLEGUIDE.txt
151 * Some company coding style: http://self.maluke.com/style 152 * Some company coding style: http://self.maluke.com/style
152 * Chandler coding style: http://chandlerproject.org/Projects/ChandlerCodingStyleGuidelines 153 * Chandler coding style: http://chandlerproject.org/Projects/ChandlerCodingStyleGuidelines
238 239
239 * Python versions to be supported 240 * Python versions to be supported
240 Support 2.4 (because some of the clusters are still running 2.4) and write 241 Support 2.4 (because some of the clusters are still running 2.4) and write
241 code that can be converted to 3.x with 2to3 in a straightforward way. 242 code that can be converted to 3.x with 2to3 in a straightforward way.
242 Task: Write to-do's and to-not-do's to avoid compatibility issues. (OD) 243 Task: Write to-do's and to-not-do's to avoid compatibility issues. (OD)
243 (DWF: Pauli Virtanen and others have put together extensive
244 documentation in the process of porting NumPy to Py3K, see his notes at
245 http://projects.scipy.org/numpy/browser/trunk/doc/Py3K.txt -- this is
246 the most complete resource for complicated combinations of Python and C).
247
248 244
249 * C coding style 245 * C coding style
250 How to write C code (in particular for Numpy / Cuda), and how to mix C and 246 How to write C code (in particular for Numpy / Cuda), and how to mix C and
251 Python. 247 Python.
252 Task: See if there would be a sensible C code style to follow (maybe look how 248 Task: See if there would be a sensible C code style to follow (maybe look how