# HG changeset patch
# User Olivier Delalleau <delallea@iro>
# Date 1283547505 14400
# Node ID 1c96e7ad95c3428c60371283cf8252a08f76b83f
# Parent  f3801e0e3913e9755f809cbe380751c0c6d2cb9e
coding_style: Added discussion point about backward compatibility with Python 2.x versions

diff -r f3801e0e3913 -r 1c96e7ad95c3 doc/v2_planning/coding_style.txt
--- a/doc/v2_planning/coding_style.txt	Fri Sep 03 16:31:06 2010 -0400
+++ b/doc/v2_planning/coding_style.txt	Fri Sep 03 16:58:25 2010 -0400
@@ -8,8 +8,8 @@
 - David
 - Olivier D [leader unless David wants to be]
 
-Existing Python coding style specifications and guidelines:
------------------------------------------------------------
+Existing Python coding style specifications and guidelines
+----------------------------------------------------------
 
     * http://www.python.org/dev/peps/pep-0008/
     * http://google-styleguide.googlecode.com/svn/trunk/pyguide.html
@@ -28,19 +28,20 @@
 We will probably want to take PEP-8 as starting point, and read what other
 people think about it / how other coding guidelines differ from it.
 
-Documentation:
---------------
+Documentation
+-------------
 
 How do we write doc?
 
-Python 3:
----------
+Compatibility with various Python versions
+------------------------------------------
 
-Is it reasonable to have coding guidelines that would make the code as
+    * Which Python 2.x version do we want to support?
+
+    * Is it reasonable to have coding guidelines that would make the code as
 compatible as possible with Python 3?
 
-
-C coding style:
----------------
+C coding style
+--------------
 
 We also need a c-style coding style.