Changeset 118 for branches/timadditionaltypes/pyramid/test/testdata/build_tests/firstpythontest/expected/dev/intro/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/intro/index.html
r100 r118 47 47 48 48 <div id="breadcrumb"><a href="/dev">python-dev</a> <span class="breadcrumb-separator">></span> Intro to Development</div> 49 <div class="section" id="guido-some-guys-and-a-mailing-list-how-python-is-developed">50 <h1><a name="guido-some-guys-and-a-mailing-list-how-python-is-developed">Guido, Some Guys, and a Mailing List: How Python is Developed</a></h1>49 <div class="section"> 50 <h1><a id="guido-some-guys-and-a-mailing-list-how-python-is-developed" name="guido-some-guys-and-a-mailing-list-how-python-is-developed">Guido, Some Guys, and a Mailing List: How Python is Developed</a></h1> 51 51 <p>by Brett Cannon (brett at python.org)</p> 52 <div class="section" id="introduction">53 <h2><a name="introduction">Introduction</a></h2>52 <div class="section"> 53 <h2><a id="introduction" name="introduction">Introduction</a></h2> 54 54 <p>Software does not make itself. Code does not spontaneously come from 55 55 the ether of the universe. <a class="reference" href="http://www.python.org/">Python</a> is no exception to this rule. … … 65 65 people from contributing to the development of Python.</p> 66 66 </div> 67 <div class="section" id="tools-used">68 <h2><a name="tools-used">Tools Used</a></h2>67 <div class="section"> 68 <h2><a id="tools-used" name="tools-used">Tools Used</a></h2> 69 69 <p>To help facilitate the development of Python, certain tools are used. 70 70 Beyond the obvious ones such as a text editor and email client, two … … 81 81 a multitude of tutorials spread across the web.</p> 82 82 </div> 83 <div class="section" id="communicating">84 <h2><a name="communicating">Communicating</a></h2>83 <div class="section"> 84 <h2><a id="communicating" name="communicating">Communicating</a></h2> 85 85 <p>Python development is not just programming. It requires a great deal 86 86 of communication between people. This communication is not just … … 96 96 realize, though, this list is meant for the discussion of the 97 97 development <em>of</em> Python; all other questions (including those about 98 development <em>in</em> Python) should be directed somewhere else, such as 99 <a class="reference" href="http://mail.python.org/mailman/listinfo/python-list">python-list</a>. Along with this, a level of etiquette is expected 98 development <em>in</em> Python) should be directed somewhere else, such as 99 <a class="reference" href="http://mail.python.org/mailman/listinfo/python-list">python-list</a>. Along with this, a level of etiquette is expected 100 100 to be maintained. A lack of manners will not be tolerated.</p> 101 101 <p>When the greater Python community is involved in a discussion, it … … 124 124 list to subscribe to if you can handle the volume of email.</p> 125 125 </div> 126 <div class="section" id="the-actual-development">127 <h2><a name="the-actual-development">The Actual Development</a></h2>126 <div class="section"> 127 <h2><a id="the-actual-development" name="the-actual-development">The Actual Development</a></h2> 128 128 <p>Developing Python is not all just conversations about neat new 129 129 language features (although those neat conversations do come up and … … 134 134 </div> 135 135 </div> 136 <div class="section" id="general-sourceforge-guidelines">137 <h1><a name="general-sourceforge-guidelines">General SourceForge Guidelines</a></h1>136 <div class="section"> 137 <h1><a id="general-sourceforge-guidelines" name="general-sourceforge-guidelines">General SourceForge Guidelines</a></h1> 138 138 <p>Since a good amount of Python development involves using <a class="reference" href="http://sourceforge.net/projects/python/">SourceForge</a>, 139 139 it is important to follow some guidelines when handling a tracker item … … 148 148 <p>Make sure you do a cursory check to make sure what ever you are 149 149 submitting was not previously submitted by someone else. Duplication 150 just uses up valuable time. If you must create a new item (for 150 just uses up valuable time. If you must create a new item (for 151 151 instance, you are posting a patch for a bug report), please place 152 152 cross-references in both tracker items.</p> … … 159 159 reasonable.</p> 160 160 </div> 161 <div class="section" id="feature-requests">162 <h1><a name="feature-requests">Feature Requests</a></h1>161 <div class="section"> 162 <h1><a id="feature-requests" name="feature-requests">Feature Requests</a></h1> 163 163 <p>A <a class="reference" href="http://sourceforge.net/tracker/?group_id=5470&atid=355470">feature request</a> means you have no plans on actually implementing 164 164 your idea by writing a patch. … … 175 175 lost in the noise as time passes.</p> 176 176 </div> 177 <div class="section" id="bug-reports">178 <h1><a name="bug-reports">Bug Reports</a></h1>177 <div class="section"> 178 <h1><a id="bug-reports" name="bug-reports">Bug Reports</a></h1> 179 179 <p>Think you found a bug? Then submit a <a class="reference" href="http://sourceforge.net/tracker/?group_id=5470&atid=105470">bug report</a> on SourceForge. 180 180 Make sure you clearly specify what version of Python you are using, … … 183 183 will not be wasted requesting more information from you.</p> 184 184 </div> 185 <div class="section" id="patches">186 <h1><a name="patches">Patches</a></h1>185 <div class="section"> 186 <h1><a id="patches" name="patches">Patches</a></h1> 187 187 <p>Create a <a class="reference" href="http://sourceforge.net/tracker/?group_id=5470&atid=305470">patch</a> tracker item on SourceForge for any code you think 188 188 should be applied to the Python CVS tree. For practically any change … … 215 215 though, is to sign the copyright over to the Python Software 216 216 Foundation.</p> 217 <p>When you think you're ready, review your own patch (see the 218 instructions in <a class="reference" href="#helping-out">Helping Out</a>). Then try to review a few 217 <p>When you think you're ready, review your own patch (see the 218 instructions in <a class="reference" href="#helping-out">Helping Out</a>). Then try to review a few 219 219 other patches as well; many patches are never applied because 220 220 no one has the time to review them. If you review enough patches 221 221 from other people, someone with checkin privileges is more likely 222 222 to spend some time on your patch.</p> 223 <div class="section" id="changing-the-language">224 <h2><a name="changing-the-language">Changing the Language</a></h2>223 <div class="section"> 224 <h2><a id="changing-the-language" name="changing-the-language">Changing the Language</a></h2> 225 225 <p>You understand how to file a patch. You think you have a great idea 226 226 on how Python should change. You are ready to write code for your … … 231 231 </div> 232 232 </div> 233 <div class="section" id="changes-to-the-stdlib">234 <h1><a name="changes-to-the-stdlib">Changes to the stdlib</a></h1>233 <div class="section"> 234 <h1><a id="changes-to-the-stdlib" name="changes-to-the-stdlib">Changes to the stdlib</a></h1> 235 235 <p>Changes to the stdlib can consist of adding functionality or changing 236 236 existing functionality.</p> … … 252 252 will reject the module. There is also the possibility of having to 253 253 write a <a class="reference" href="http://www.python.org/peps/pep-0001.html">PEP</a> (read about PEPs in <a class="reference" href="#changing-the-language-proper">Changing the Language Proper</a>).</p> 254 <p>Guido has also stated that for any new module it has to have been 255 accepted and widely used by the greater Python community before it 256 can be considered for addition to the stdlib. This is to prevent 257 bloat in the stdlib by making sure that any new modules will actually 258 be used and not just by the person who wrote the module and a few 254 <p>Guido has also stated that for any new module it has to have been 255 accepted and widely used by the greater Python community before it 256 can be considered for addition to the stdlib. This is to prevent 257 bloat in the stdlib by making sure that any new modules will actually 258 be used and not just by the person who wrote the module and a few 259 259 people who supported its addition.</p> 260 260 <p>Changing existing functionality can be difficult to do if it breaks … … 264 264 dev as a whole to agree to the change.</p> 265 265 </div> 266 <div class="section" id="changing-the-language-proper">267 <h1><a name="changing-the-language-proper">Changing the Language Proper</a></h1>266 <div class="section"> 267 <h1><a id="changing-the-language-proper" name="changing-the-language-proper">Changing the Language Proper</a></h1> 268 268 <p>Changing Python the language is taken <strong>very</strong> seriously. Python is 269 269 often heralded for its simplicity and cleanliness. Any additions to … … 286 286 <p>As with all new code make sure you also have appropriate documentation 287 287 patches along with tests for the new functionality.</p> 288 <div class="section" id="helping-out">289 <h2><a name="helping-out">Helping Out</a></h2>288 <div class="section"> 289 <h2><a id="helping-out" name="helping-out">Helping Out</a></h2> 290 290 <p>Many people say they wish they could help out with the development of 291 291 Python but feel they are not up to writing code. There are plenty of 292 292 things one can do, though, that does not necessarily require you to write code. 293 293 Regardless of your coding abilities, there is something for everyone 294 to help with. Below is an attempt to discuss all possible options one has in 294 to help with. Below is an attempt to discuss all possible options one has in 295 295 helping out with development.</p> 296 296 <p>For <strong>feature requests</strong>, adding a comment about what you think is … … 301 301 can be extremely helpful. (Do give details about your system; if the 302 302 bug shows up only on Linux, or only on Windows XP, that makes it easier 303 to track down.) If you can write a fix for the bug that is very helpful 303 to track down.) If you can write a fix for the bug that is very helpful 304 304 as well; start a patch item and reference it in a comment in the bug item.</p> 305 <p>There is always a need for more people to <strong>test and review patches!</strong> 305 <p>There is always a need for more people to <strong>test and review patches!</strong> 306 306 Apply the patch and run the testing suite. You can do a 307 307 code review on the patch to make sure that it is good, clean code. If … … 330 330 <p>If there is nothing specific you find you want to work on but still 331 331 feel like contributing nonetheless, there are several things you can 332 do. The <strong>documentation</strong> can always use fleshing out. 332 do. The <strong>documentation</strong> can always use fleshing out. 333 333 <strong>Adding more tests</strong> to the testing suite is always useful. 334 334 Running the test suite itself (see the documentation for the 'test' … … 343 343 on the CVS tree. It is a great way to learn how to work in a large, 344 344 distributed group along with how to write great code.</p> 345 <p>And if all else fails give <strong>money</strong>; the <a class="reference" href="http://www.python.org/psf/">Python Software Foundation</a> 345 <p>And if all else fails give <strong>money</strong>; the <a class="reference" href="http://www.python.org/psf/">Python Software Foundation</a> 346 346 is a non-profit organization that accepts donations that are tax- 347 347 deductible in the United States. The funds are used for various thing … … 352 352 Every dollar does help, so please contribute if you can.</p> 353 353 </div> 354 <div class="section" id="conclusion">355 <h2><a name="conclusion">Conclusion</a></h2>354 <div class="section"> 355 <h2><a id="conclusion" name="conclusion">Conclusion</a></h2> 356 356 <p>If you get any message from this document, it should be that <em>anyone</em> 357 357 can help with the development of Python. All help is greatly
