Changeset 118 for branches/timadditionaltypes/pyramid/test/testdata/build_tests/firstpythontest/expected/dev/patches/style2/subnav1/a/index.html
- Timestamp:
- 02/04/06 19:29:16 (3 years ago)
- Files:
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
branches/timadditionaltypes/pyramid/test/testdata/build_tests/firstpythontest/expected/dev/patches/style2/subnav1/a/index.html
r100 r118 47 47 48 48 <div id="breadcrumb"><a href="/dev">python-dev</a> <span class="breadcrumb-separator">></span> <a href="/dev/patches">Patch Submission</a> <span class="breadcrumb-separator">></span> <a href="/dev/patches/style2">Dummy Entry</a> <span class="breadcrumb-separator">></span> <a href="/dev/patches/style2/subnav1">samplesub1</a> <span class="breadcrumb-separator">></span> a</div> 49 <div class="section" id="python-patch-style-guidelines">50 <h1><a name="python-patch-style-guidelines">Python Patch Style Guidelines</a></h1>49 <div class="section"> 50 <h1><a id="python-patch-style-guidelines" name="python-patch-style-guidelines">Python Patch Style Guidelines</a></h1> 51 51 <p>Here are some style guidelines for the production of high quality 52 patches to Python. See the <a class="reference" href="./">patch submission guidelines</a> 52 patches to Python. See the <a class="reference" href="./">patch submission guidelines</a> 53 53 for additional requirements (such as legal boilerplate, 54 54 the use of context diffs, and where to mail patches).</p> … … 67 67 lines fit in 78 columns.</strong> When submitting C code, don't use C++ 68 68 style (//) comments. Write function and method calls like this: 69 <tt class="docutils literal"><span class="pre">foo(arg1,</span> <span class="pre">arg2)</span></tt>; not like this <tt class="docutils literal"><span class="pre">foo(</span> <span class="pre">arg1,</span> <span class="pre">arg2</span> <span class="pre">)</span></tt> 69 <tt class="docutils literal"><span class="pre">foo(arg1,</span> <span class="pre">arg2)</span></tt>; not like this <tt class="docutils literal"><span class="pre">foo(</span> <span class="pre">arg1,</span> <span class="pre">arg2</span> <span class="pre">)</span></tt> 70 70 nor like this: <tt class="docutils literal"><span class="pre">foo</span> <span class="pre">(arg1,</span> <span class="pre">arg2)</span></tt>. The following 71 71 statements are <em>not</em> function calls and do not require 72 72 parentheses: <tt class="docutils literal"><span class="pre">return</span></tt>, <tt class="docutils literal"><span class="pre">del</span></tt>, <tt class="docutils literal"><span class="pre">exec</span></tt>, 73 <tt class="docutils literal"><span class="pre">raise</span></tt>, <tt class="docutils literal"><span class="pre">print</span></tt>. 74 See <a class="reference" href="http://www.python.org/peps/pep-0008.html">PEP 8: Python Style Guide</a> 73 <tt class="docutils literal"><span class="pre">raise</span></tt>, <tt class="docutils literal"><span class="pre">print</span></tt>. 74 See <a class="reference" href="http://www.python.org/peps/pep-0008.html">PEP 8: Python Style Guide</a> 75 75 for more notes on the preferred coding style.</li> 76 76 <li>When you have to patch the C source to make it work on a
