# HG changeset patch # User Olivier Delalleau # Date 1284579525 14400 # Node ID 0653a85ff2e88edc2d3ea7027e453fc249b8ceb4 # Parent 9baa47482ccc9acb914080337edc836efb95c313 coding_style: Moved url about Numpy conversion to Python 3 to the url list diff -r 9baa47482ccc -r 0653a85ff2e8 doc/v2_planning/coding_style.txt --- a/doc/v2_planning/coding_style.txt Wed Sep 15 15:20:13 2010 -0400 +++ b/doc/v2_planning/coding_style.txt Wed Sep 15 15:38:45 2010 -0400 @@ -145,6 +145,7 @@ * Google Python Style Guide: http://google-styleguide.googlecode.com/svn/trunk/pyguide.html * Interesting * Code Like a Pythonista: http://python.net/~goodger/projects/pycon/2007/idiomatic/handout.html + * Numpy notes on conversion to Python 3: http://projects.scipy.org/numpy/browser/trunk/doc/Py3K.txt * Can skip * Python style for university class: http://www.cs.caltech.edu/courses/cs11/material/python/misc/python_style_guide.html * Mailman coding style: http://barry.warsaw.us/software/STYLEGUIDE.txt @@ -240,11 +241,6 @@ Support 2.4 (because some of the clusters are still running 2.4) and write code that can be converted to 3.x with 2to3 in a straightforward way. Task: Write to-do's and to-not-do's to avoid compatibility issues. (OD) -(DWF: Pauli Virtanen and others have put together extensive -documentation in the process of porting NumPy to Py3K, see his notes at -http://projects.scipy.org/numpy/browser/trunk/doc/Py3K.txt -- this is -the most complete resource for complicated combinations of Python and C). - * C coding style How to write C code (in particular for Numpy / Cuda), and how to mix C and