Changeset 118 for branches/timadditionaltypes/pyramid/test/testdata/build_tests/firstpythontest/expected/dev/tools/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/tools/index.html
r100 r118 47 47 48 48 <div id="breadcrumb"><a href="/dev">python-dev</a> <span class="breadcrumb-separator">></span> Tools</div> 49 <div class="section" id="python-tools">50 <h1><a name="python-tools">Python Tools</a></h1>51 <div class="section" id="cvs-tree">52 <h2><a name="cvs-tree">CVS Tree</a></h2>49 <div class="section"> 50 <h1><a id="python-tools" name="python-tools">Python Tools</a></h1> 51 <div class="section"> 52 <h2><a id="cvs-tree" name="cvs-tree">CVS Tree</a></h2> 53 53 <p>The Python source code is stored in the CVS version control system. 54 54 In May 2000, the Python CVS tree was moved to <a class="reference" href="http://www.sf.net">SourceForge</a>. Using SourceForge's … … 65 65 <p>Then, you can check out the tree:</p> 66 66 <pre class="literal-block"> 67 cvs -z3 \ 67 cvs -z3 \ 68 68 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/python \ 69 69 co python … … 78 78 <a class="reference" href="http://www.cvshome.org/docs/manual/">http://www.cvshome.org/docs/manual/</a>. Pay particular attention to 79 79 section 1.3 for a sample CVS session.</p> 80 <div class="section" id="check-in-policies">81 <h3><a name="check-in-policies">Check-in Policies</a></h3>80 <div class="section"> 81 <h3><a id="check-in-policies" name="check-in-policies">Check-in Policies</a></h3> 82 82 <p>Write access to the Python CVS tree is not automatically granted, 83 83 though there's no formal process to go through to get it. If the … … 109 109 ./python ./Lib/test/testall.py 110 110 </pre> 111 <p>If the module you're modifying doesn't have a test suite, you 111 <p>If the module you're modifying doesn't have a test suite, you 112 112 could consider writing a set of test cases for it.</p> 113 113 </li> … … 123 123 <li><p class="first">When a patch changes behavior or fixes a noteworthy bug, you 124 124 should add an entry to the <tt class="docutils literal"><span class="pre">Misc/NEWS</span></tt> file about the 125 change. The file is divided into sections for the core and built-ins, 125 change. The file is divided into sections for the core and built-ins, 126 126 extension modules, the standard library, and accompanying tools, 127 127 and a change should be described in the appropriate section. 128 You don't need to update the "What's New in Python" document in 128 You don't need to update the "What's New in Python" document in 129 129 <tt class="docutils literal"><span class="pre">Doc/whatsnew</span></tt>.</p> 130 130 </li> … … 157 157 </div> 158 158 </div> 159 <div class="section" id="bug-tracking">160 <h2><a name="bug-tracking">Bug Tracking</a></h2>159 <div class="section"> 160 <h2><a id="bug-tracking" name="bug-tracking">Bug Tracking</a></h2> 161 161 <p>To report a bug in Python, use <a class="reference" href="http://sourceforge.net/tracker/?group_id=5470&atid=105470">the bug tracker</a>. Don't report bugs by posting them to a mailing list or 162 162 by sending them to a particular developer as a private e-mail; most … … 169 169 once they've been reported.</p> 170 170 </div> 171 <div class="section" id="patch-tracking">172 <h2><a name="patch-tracking">Patch Tracking</a></h2>171 <div class="section"> 172 <h2><a id="patch-tracking" name="patch-tracking">Patch Tracking</a></h2> 173 173 <p>Just like bugs, and for much the same reasons, patches should be 174 174 submitted to the <a class="reference" href="http://sourceforge.net/tracker/?group_id=5470&atid=305470">patch manager</a>, and not through e-mail. Often a patch will need some … … 188 188 </ul> 189 189 </div> 190 <div class="section" id="url-redirectors">191 <h2><a name="url-redirectors">URL Redirectors</a></h2>190 <div class="section"> 191 <h2><a id="url-redirectors" name="url-redirectors">URL Redirectors</a></h2> 192 192 <p>SourceForge bug reports have long and ugly URLs:</p> 193 193 <pre class="literal-block">
