Mercurial > pylearn
comparison doc/v2_planning/coding_style.txt @ 1049:ff9361e39c97
remark on fiding tools
author | Dumitru Erhan <dumitru.erhan@gmail.com> |
---|---|
date | Wed, 08 Sep 2010 14:24:28 -0400 |
parents | f1e0a180574a |
children | 573363a9b5c7 |
comparison
equal
deleted
inserted
replaced
1048:0464f891129b | 1049:ff9361e39c97 |
---|---|
26 * http://docs.djangoproject.com/en/dev/internals/contributing/#coding-style | 26 * http://docs.djangoproject.com/en/dev/internals/contributing/#coding-style |
27 | 27 |
28 We will probably want to take PEP-8 as starting point, and read what other | 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. | 29 people think about it / how other coding guidelines differ from it. |
30 | 30 |
31 Dumi: we should also try to find tools (such as pylint) that automate these | |
32 processes. | |
33 | |
31 Documentation | 34 Documentation |
32 ------------- | 35 ------------- |
33 | 36 |
34 How do we write doc? | 37 How do we write doc? |
35 | 38 |