Mercurial > pylearn
changeset 1025:1c96e7ad95c3
coding_style: Added discussion point about backward compatibility with Python 2.x versions
| author | Olivier Delalleau <delallea@iro> |
|---|---|
| date | Fri, 03 Sep 2010 16:58:25 -0400 |
| parents | f3801e0e3913 |
| children | 38f799f8b6cd |
| files | doc/v2_planning/coding_style.txt |
| diffstat | 1 files changed, 11 insertions(+), 10 deletions(-) [+] |
line wrap: on
line diff
--- 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.