Changeset 118 for branches/timadditionaltypes/pyramid/test/testdata/build_tests/firstpythontest/expected/dev/implementations/.cache.dump
- 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/implementations/.cache.dump
r100 r118 74 74 p32 75 75 g6 76 S'<div class="section" id="python-patch-submission-guidelines">\n<h1><a name="python-patch-submission-guidelines">Python Patch Submission Guidelines</a></h1>\n<p>We\'re using the SourceForge Patch Manager. Here are the main\nguidelines:</p>\n<ul class="simple">\n<li>Submit your patch to the <a class="reference" href="http://sourceforge.net/patch/?group_id=5470">patch manager</a>\ninterface at <a class="reference" href="http://sourceforge.net/project/?group_id=5470">SourceForge</a>. \nYou will need to <a class="reference" href="http://sourceforge.net/account/register.php">register with SourceForge</a>, and you will need to <a class="reference" href="https://sourceforge.net/account/login.php">login</a>\nbefore submitting a patch, or else the \'Submit New\'\nlink will not appear. The patch manager is for\n<strong>patches</strong> only; if you have a problem or suggestion but don\'t\nknow how to write the code for it, use the <a class="reference" href="http://sourceforge.net/bugs/?group_id=5470">bug manager</a>\ninstead.</li>\n<li>Submit documentation patches the same way. When adding the\npatch, be sure to set the "Category" field to\n"documentation". For documentation errors without patches,\nplease use the <a class="reference" href="http://sourceforge.net/bugs/?group_id=5470">bugs manager</a> instead.</li>\n<li>We like context diffs. We grudgingly accept unified diffs.\nStraight ("ed-style") diffs are right out! If you don\'t know\nhow to generate context diffs, you\'re probably not qualified to\nproduce high-quality patches anyway <0.5 wink>.</li>\n<li>Please use forward diffs. That is, use "diff -c oldfile\nnewfile", and not the other way around.</li>\n<li>If you send diffs for multiple files, concatenate all the diffs in\na single text file. Please don\'t produce a zip file with multiple\npatches.</li>\n<li>We appreciate it if you send patches relative to the <a class="reference" href="http://sourceforge.net/cvs/?group_id=5470">current CVS tree</a>. These are our\nlatest sources. Even a patch relative to the latest alpha or beta\nrelease may be way out of date.</li>\n<li>Please add a succinct message to your SourceForge entry that\nexplains what the patch is about that we can use directly as a checkin\nmessage. Ideally, such a message explains the problem and describes\nthe fix in a few lines.</li>\n<li>For patches that add or change functionality: please also update\nthe <strong>documentation</strong> and the <strong>testcases</strong> (the Lib/test\nsubdirectory). For new modules, we appreciate a new test module\n(typically test/test_spam.py). In this case, there\'s no need to mail\nthe documentation to a different address (in fact, in order to verify\nthat the bundle is complete, it\'s easier to mail everything together).</li>\n<li>There are a variety of additional <a class="reference" href="/patches/style/">style requirements</a>. \nPlease have a look at these before writing new code. Also have a look at\n<a class="reference" href="http://www.python.org/peps/pep-0008.html">PEP 8: Python Style Guide</a>.</li>\n</ul>\n</div>\n'76 S'<div class="section">\n<h1><a id="python-patch-submission-guidelines" name="python-patch-submission-guidelines">Python Patch Submission Guidelines</a></h1>\n<p>We\'re using the SourceForge Patch Manager. Here are the main\nguidelines:</p>\n<ul class="simple">\n<li>Submit your patch to the <a class="reference" href="http://sourceforge.net/patch/?group_id=5470">patch manager</a>\ninterface at <a class="reference" href="http://sourceforge.net/project/?group_id=5470">SourceForge</a>.\nYou will need to <a class="reference" href="http://sourceforge.net/account/register.php">register with SourceForge</a>, and you will need to <a class="reference" href="https://sourceforge.net/account/login.php">login</a>\nbefore submitting a patch, or else the \'Submit New\'\nlink will not appear. The patch manager is for\n<strong>patches</strong> only; if you have a problem or suggestion but don\'t\nknow how to write the code for it, use the <a class="reference" href="http://sourceforge.net/bugs/?group_id=5470">bug manager</a>\ninstead.</li>\n<li>Submit documentation patches the same way. When adding the\npatch, be sure to set the "Category" field to\n"documentation". For documentation errors without patches,\nplease use the <a class="reference" href="http://sourceforge.net/bugs/?group_id=5470">bugs manager</a> instead.</li>\n<li>We like context diffs. We grudgingly accept unified diffs.\nStraight ("ed-style") diffs are right out! If you don\'t know\nhow to generate context diffs, you\'re probably not qualified to\nproduce high-quality patches anyway <0.5 wink>.</li>\n<li>Please use forward diffs. That is, use "diff -c oldfile\nnewfile", and not the other way around.</li>\n<li>If you send diffs for multiple files, concatenate all the diffs in\na single text file. Please don\'t produce a zip file with multiple\npatches.</li>\n<li>We appreciate it if you send patches relative to the <a class="reference" href="http://sourceforge.net/cvs/?group_id=5470">current CVS tree</a>. These are our\nlatest sources. Even a patch relative to the latest alpha or beta\nrelease may be way out of date.</li>\n<li>Please add a succinct message to your SourceForge entry that\nexplains what the patch is about that we can use directly as a checkin\nmessage. Ideally, such a message explains the problem and describes\nthe fix in a few lines.</li>\n<li>For patches that add or change functionality: please also update\nthe <strong>documentation</strong> and the <strong>testcases</strong> (the Lib/test\nsubdirectory). For new modules, we appreciate a new test module\n(typically test/test_spam.py). In this case, there\'s no need to mail\nthe documentation to a different address (in fact, in order to verify\nthat the bundle is complete, it\'s easier to mail everything together).</li>\n<li>There are a variety of additional <a class="reference" href="/patches/style/">style requirements</a>.\nPlease have a look at these before writing new code. Also have a look at\n<a class="reference" href="http://www.python.org/peps/pep-0008.html">PEP 8: Python Style Guide</a>.</li>\n</ul>\n</div>\n' 77 77 tRp33 78 78 sS'breadcrumb' … … 641 641 sg25 642 642 (dp286 643 S' utility'643 S'title' 644 644 p287 645 (lp288 646 (dp289 647 g37 648 S'/help' 649 p290 650 sg39 651 S'help' 645 S'The Official Python Programming Language Website' 646 p288 647 sS'metadata' 648 p289 649 (dp290 650 S'keywords' 652 651 p291 653 sa(dp292 654 g37 655 S'/sitemap'652 S'python programming language object oriented web free source' 653 p292 654 sS'description' 656 655 p293 657 sg39 658 S'sitemap' 656 S'Home page for Python, an interpreted, interactive, object-oriented, extensible programming language. It provides an extraordinary combination of clarity and versatility, and is free and comprehensively ported.\n' 659 657 p294 660 s asS'metadata'658 ssS'nav' 661 659 p295 662 (dp296663 S'keywords'664 p297665 S'python programming language object oriented web free source'666 p298667 sS'description'668 p299669 S'Home page for Python, an interpreted, interactive, object-oriented, extensible programming language. It provides an extraordinary combination of clarity and versatility, and is free and comprehensively ported.\n'670 p300671 ssS'nav'672 p301673 660 (ipyramid.yamlRegistry 674 661 fragmentFile 675 p 302676 (dp 303662 p296 663 (dp297 677 664 g23 678 665 g49 679 sbsS'title' 666 sbsS'utility' 667 p298 668 (lp299 669 (dp300 670 g37 671 S'/help' 672 p301 673 sg39 674 S'help' 675 p302 676 sa(dp303 677 g37 678 S'/sitemap' 680 679 p304 681 S'The Official Python Programming Language Website' 680 sg39 681 S'sitemap' 682 682 p305 683 s sg27683 sassg27 684 684 (dp306 685 685 S'content' … … 717 717 p321 718 718 (dp322 719 S' breadcrumb'719 S'text' 720 720 p323 721 (lp324722 (dp325723 g37724 S'/dev'725 p326726 sg39727 S'python-dev'728 p327729 sa(dp328730 g37731 S'/dev/patches'732 p329733 sg39734 S'Patch Submission'735 p330736 sa(dp331737 g37738 S'/dev/patches/style2'739 p332740 sg39741 S'Dummy Entry'742 p333743 sasS'text'744 p334745 721 g4 746 722 (g32 747 723 g6 748 S'<div class="section" id="python-patch-style-guidelines">\n<h1><a name="python-patch-style-guidelines">Python Patch Style Guidelines</a></h1>\n<p>Here are some style guidelines for the production of high quality\npatches to Python. See the <a class="reference" href="./">patch submission guidelines</a> \nfor additional requirements (such as legal boilerplate,\nthe use of context diffs, and where to mail patches).</p>\n<ul class="simple">\n<li>Don\'t annotate your changes with comments like "# My patch here"\nor "# Patched because of ..."; if you have to explain the patch, do so\nin the text leading up to the message. (On the other hand, if your\npatch introduces new code or deals with a tricky situation, comments\nare welcome, of course.)</li>\n<li>Please match the existing coding style whenever you can. Use the\nexisting indentation style in the file you are editing. (There are\ntwo styles: some files use tabs exclusively for indentation, others\nuse 4-space indents. The latter is preferred for new files. A tab\ncharacter should <em>always</em> be equivalent to 8 spaces, not 4 as is\nthe default in most editors on Mac and Windows.) <strong>Make sure all\nlines fit in 78 columns.</strong> When submitting C code, don\'t use C++\nstyle (//) comments. Write function and method calls like this:\n<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> \nnor like this: <tt class="docutils literal"><span class="pre">foo</span> <span class="pre">(arg1,</span> <span class="pre">arg2)</span></tt>. The following\nstatements are <em>not</em> function calls and do not require\nparentheses: <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>,\n<tt class="docutils literal"><span class="pre">raise</span></tt>, <tt class="docutils literal"><span class="pre">print</span></tt>. \nSee <a class="reference" href="http://www.python.org/peps/pep-0008.html">PEP 8: Python Style Guide</a> \nfor more notes on the preferred coding style.</li>\n<li>When you have to patch the C source to make it work on a\nparticular platform, please make sure to use the appropriate\n<tt class="docutils literal"><span class="pre">#ifdef...#endif</span></tt> bracket to avoid enabling the code on other platforms\n(unless the patch is portable). Read your C compiler or C\npreprocessor documentation to select the right predefined symbol to\ntest.</li>\n</ul>\n</div>\n' 749 tRp335 750 sS'subnav' 724 S'<div class="section">\n<h1><a id="python-patch-style-guidelines" name="python-patch-style-guidelines">Python Patch Style Guidelines</a></h1>\n<p>Here are some style guidelines for the production of high quality\npatches to Python. See the <a class="reference" href="./">patch submission guidelines</a>\nfor additional requirements (such as legal boilerplate,\nthe use of context diffs, and where to mail patches).</p>\n<ul class="simple">\n<li>Don\'t annotate your changes with comments like "# My patch here"\nor "# Patched because of ..."; if you have to explain the patch, do so\nin the text leading up to the message. (On the other hand, if your\npatch introduces new code or deals with a tricky situation, comments\nare welcome, of course.)</li>\n<li>Please match the existing coding style whenever you can. Use the\nexisting indentation style in the file you are editing. (There are\ntwo styles: some files use tabs exclusively for indentation, others\nuse 4-space indents. The latter is preferred for new files. A tab\ncharacter should <em>always</em> be equivalent to 8 spaces, not 4 as is\nthe default in most editors on Mac and Windows.) <strong>Make sure all\nlines fit in 78 columns.</strong> When submitting C code, don\'t use C++\nstyle (//) comments. Write function and method calls like this:\n<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>\nnor like this: <tt class="docutils literal"><span class="pre">foo</span> <span class="pre">(arg1,</span> <span class="pre">arg2)</span></tt>. The following\nstatements are <em>not</em> function calls and do not require\nparentheses: <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>,\n<tt class="docutils literal"><span class="pre">raise</span></tt>, <tt class="docutils literal"><span class="pre">print</span></tt>.\nSee <a class="reference" href="http://www.python.org/peps/pep-0008.html">PEP 8: Python Style Guide</a>\nfor more notes on the preferred coding style.</li>\n<li>When you have to patch the C source to make it work on a\nparticular platform, please make sure to use the appropriate\n<tt class="docutils literal"><span class="pre">#ifdef...#endif</span></tt> bracket to avoid enabling the code on other platforms\n(unless the patch is portable). Read your C compiler or C\npreprocessor documentation to select the right predefined symbol to\ntest.</li>\n</ul>\n</div>\n' 725 tRp324 726 sS'breadcrumb' 727 p325 728 (lp326 729 (dp327 730 g37 731 S'/dev' 732 p328 733 sg39 734 S'python-dev' 735 p329 736 sa(dp330 737 g37 738 S'/dev/patches' 739 p331 740 sg39 741 S'Patch Submission' 742 p332 743 sa(dp333 744 g37 745 S'/dev/patches/style2' 746 p334 747 sg39 748 S'Dummy Entry' 749 p335 750 sasS'subnav' 751 751 p336 752 752 g4 … … 1304 1304 (dp518 1305 1305 g287 1306 (lp519 1307 (dp520 1308 g37 1309 g290 1310 sg39 1306 g288 1307 sg289 1308 (dp519 1311 1309 g291 1312 sa(dp521 1313 g37 1314 g293 1315 sg39 1310 g292 1311 sg293 1316 1312 g294 1317 sasg295 1318 (dp522 1319 g297 1320 g298 1321 sg299 1322 g300 1323 ssg301 1313 ssg295 1324 1314 (ipyramid.yamlRegistry 1325 1315 fragmentFile 1326 p52 31327 (dp52 41316 p520 1317 (dp521 1328 1318 g23 1329 1319 g49 1330 sbsg304 1320 sbsg298 1321 (lp522 1322 (dp523 1323 g37 1324 g301 1325 sg39 1326 g302 1327 sa(dp524 1328 g37 1329 g304 1330 sg39 1331 1331 g305 1332 s sg271332 sassg27 1333 1333 (dp525 1334 1334 S'content' … … 1371 1371 (g32 1372 1372 g6 1373 S'<div class="section" id="can-t-find-what-you-re-looking-for">\n<h1><a name="can-t-find-what-you-re-looking-for">Can\'t find what you\'re looking for?</a></h1>\n<div class="section" id="new-to-programming-and-to-python">\n<h2><a name="new-to-programming-and-to-python">New to programming and to Python?</a></h2>\n<ul class="simple">\n<li>Check out the <a class="reference" href="http://www.python.org/moin/BeginnersGuide">Beginner\'s Guide</a>.</li>\n</ul>\n</div>\n<div class="section" id="new-to-python">\n<h2><a name="new-to-python">New to Python?</a></h2>\n<ul class="simple">\n<li>The standard <a class="reference" href="doc/current/tut/tut.html">tutorial</a> is available for\nonline browsing and downloading from the <a class="reference" href="doc/">documentation</a> web page.</li>\n<li>A growing number of <a class="reference" href="http://www.python.org/moin/PythonBooks">Python books</a> is available at\nyour local bookstore.</li>\n<li>Many good examples of Python coding can be found in the standard libraries\n<a class="reference" href="download/">distributed</a> with Python.</li>\n</ul>\n</div>\n<div class="section" id="looking-for-downloads">\n<h2><a name="looking-for-downloads">Looking for downloads?</a></h2>\n<ul class="simple">\n<li>See the <a class="reference" href="download/">download page</a> for links to the important downloads.</li>\n</ul>\n</div>\n<div class="section" id="got-a-python-problem-or-question">\n<h2><a name="got-a-python-problem-or-question">Got a Python problem or question?</a></h2>\n<ul class="simple">\n<li>First check the <a class="reference" href="doc/faq/">Python FAQs</a>, with answers to many common,\ngeneral Python questions.</li>\n<li>If you suspect a bug in the Python core, search the <a class="reference" href="http://sourceforge.net/tracker/?group_id=5470&atid=105470">Python Bug Tracker</a>.</li>\n<li>For Python CGI questions, try Dave Mitchell\'s <a class="reference" href="http://starship.python.net/crew/davem/cgifaq/faqw.cgi">Python CGI FAQ</a> on Starship.</li>\n<li><a class="reference" href="mailto:python-help@python.org">python-help@python.org</a>\n(a.k.a. <a class="reference" href="mailto:help@python.org">help@python.org</a>) reaches a volunteer\nteam of crack Python experts. (When posing questions, take care - the\nbetter your details - including exact error messages, system\nconfiguration, etc - the more likely the helpers will be able to grasp\nwhat\'s going on.) More info: <a class="reference" href="community/lists.html#help">Python-help description</a>.</li>\n<li>The Python newsgroup, <a class="reference" href="news:comp.lang.python">comp.lang.python</a>, reaches\nmany many people, some of whom may already have hit and surmounted your\nproblem. Also available as a maillist - for more info, see <a class="reference" href="community/lists.html#clp">the newsgroup\ndescription</a>.</li>\n</ul>\n</div>\n<div class="section" id="looking-for-a-particular-python-module-or-application">\n<h2><a name="looking-for-a-particular-python-module-or-application">Looking for a particular Python module or application?</a></h2>\n<ul class="simple">\n<li>Try the <a class="reference" href="search/">python.org search engines</a> - you can\nfind anything mentioned on the Python site, in the <a class="reference" href="doc/faq/">FAQ</a>, on\n<a class="reference" href="http://starship.python.net/">the starship</a>, or in the newsgroup (see\nabove). More info: <a class="reference" href="search/#help">where to search</a>.</li>\n<li>Find out about <a class="reference" href="download/Contributed.html">other Python software</a> around\nthe net.</li>\n<li>The <a class="reference" href="sigs/">Python Special Interest Groups (SIGS)</a>\nprovide a focus for concerted, active development efforts - check there to\nsee whether one on your topic of concern already exists, or whether it\nmakes sense to start one.</li>\n</ul>\n</div>\n<div class="section" id="want-to-contribute">\n<h2><a name="want-to-contribute">Want to contribute?</a></h2>\n<ul class="simple">\n<li>To report a bug in the Python core, use the <a class="reference" href="http://sourceforge.net/tracker/?group_id=5470&atid=105470">Python Bug Tracker</a> at\nSourceForge.</li>\n<li>To contribute a bug fix or other patch to the Python\ncore, see the <a class="reference" href="/dev/">Python Developer\'s Guide</a>.</li>\n<li>To contribute to the official <a class="reference" href="doc/">Python documentation</a>, write to\n<a class="reference" href="mailto:docs@python.org">docs@python.org</a>, or use the <a class="reference" href="http://sourceforge.net/tracker/?group_id=5470&atid=305470">Patch Manger</a> to\ncontribute a documentation patch.</li>\n<li>To announce your module or application to the Python community,\nuse <a class="reference" href="news:comp.lang.python.announce">comp.lang.python.announce</a> (or via\nemail, <a class="reference" href="mailto:python-announce@python.org">python-announce@python.org</a>,\nif you lack news access). More info: <a class="reference" href="community/lists.html#clpa">the announcements newsgroup\ndescription</a></li>\n<li>To propose changes to the python core, post your thoughts to\n<a class="reference" href="news:comp.lang.python">comp.lang.python</a>. If you have an\nimplementation, follow the <a class="reference" href="/patches/">Python Patch Guidelines</a>.</li>\n</ul>\n</div>\n<div class="section" id="did-we-miss-your-concern">\n<h2><aname="did-we-miss-your-concern">Did we miss your concern?</a></h2>\n<ul class="simple">\n<li>Contact <a class="reference" href="mailto:webmaster@python.org">webmaster@python.org</a> and let us\nknow how we can help!</li>\n</ul>\n</div>\n</div>\n'1373 S'<div class="section">\n<h1><a id="can-t-find-what-you-re-looking-for" name="can-t-find-what-you-re-looking-for">Can\'t find what you\'re looking for?</a></h1>\n<div class="section">\n<h2><a id="new-to-programming-and-to-python" name="new-to-programming-and-to-python">New to programming and to Python?</a></h2>\n<ul class="simple">\n<li>Check out the <a class="reference" href="http://www.python.org/moin/BeginnersGuide">Beginner\'s Guide</a>.</li>\n</ul>\n</div>\n<div class="section">\n<h2><a id="new-to-python" name="new-to-python">New to Python?</a></h2>\n<ul class="simple">\n<li>The standard <a class="reference" href="doc/current/tut/tut.html">tutorial</a> is available for\nonline browsing and downloading from the <a class="reference" href="doc/">documentation</a> web page.</li>\n<li>A growing number of <a class="reference" href="http://www.python.org/moin/PythonBooks">Python books</a> is available at\nyour local bookstore.</li>\n<li>Many good examples of Python coding can be found in the standard libraries\n<a class="reference" href="download/">distributed</a> with Python.</li>\n</ul>\n</div>\n<div class="section">\n<h2><a id="looking-for-downloads" name="looking-for-downloads">Looking for downloads?</a></h2>\n<ul class="simple">\n<li>See the <a class="reference" href="download/">download page</a> for links to the important downloads.</li>\n</ul>\n</div>\n<div class="section">\n<h2><a id="got-a-python-problem-or-question" name="got-a-python-problem-or-question">Got a Python problem or question?</a></h2>\n<ul class="simple">\n<li>First check the <a class="reference" href="doc/faq/">Python FAQs</a>, with answers to many common,\ngeneral Python questions.</li>\n<li>If you suspect a bug in the Python core, search the <a class="reference" href="http://sourceforge.net/tracker/?group_id=5470&atid=105470">Python Bug Tracker</a>.</li>\n<li>For Python CGI questions, try Dave Mitchell\'s <a class="reference" href="http://starship.python.net/crew/davem/cgifaq/faqw.cgi">Python CGI FAQ</a> on Starship.</li>\n<li><a class="reference" href="mailto:python-help@python.org">python-help@python.org</a>\n(a.k.a. <a class="reference" href="mailto:help@python.org">help@python.org</a>) reaches a volunteer\nteam of crack Python experts. (When posing questions, take care - the\nbetter your details - including exact error messages, system\nconfiguration, etc - the more likely the helpers will be able to grasp\nwhat\'s going on.) More info: <a class="reference" href="community/lists.html#help">Python-help description</a>.</li>\n<li>The Python newsgroup, <a class="reference" href="news:comp.lang.python">comp.lang.python</a>, reaches\nmany many people, some of whom may already have hit and surmounted your\nproblem. Also available as a maillist - for more info, see <a class="reference" href="community/lists.html#clp">the newsgroup\ndescription</a>.</li>\n</ul>\n</div>\n<div class="section">\n<h2><a id="looking-for-a-particular-python-module-or-application" name="looking-for-a-particular-python-module-or-application">Looking for a particular Python module or application?</a></h2>\n<ul class="simple">\n<li>Try the <a class="reference" href="search/">python.org search engines</a> - you can\nfind anything mentioned on the Python site, in the <a class="reference" href="doc/faq/">FAQ</a>, on\n<a class="reference" href="http://starship.python.net/">the starship</a>, or in the newsgroup (see\nabove). More info: <a class="reference" href="search/#help">where to search</a>.</li>\n<li>Find out about <a class="reference" href="download/Contributed.html">other Python software</a> around\nthe net.</li>\n<li>The <a class="reference" href="sigs/">Python Special Interest Groups (SIGS)</a>\nprovide a focus for concerted, active development efforts - check there to\nsee whether one on your topic of concern already exists, or whether it\nmakes sense to start one.</li>\n</ul>\n</div>\n<div class="section">\n<h2><a id="want-to-contribute" name="want-to-contribute">Want to contribute?</a></h2>\n<ul class="simple">\n<li>To report a bug in the Python core, use the <a class="reference" href="http://sourceforge.net/tracker/?group_id=5470&atid=105470">Python Bug Tracker</a> at\nSourceForge.</li>\n<li>To contribute a bug fix or other patch to the Python\ncore, see the <a class="reference" href="/dev/">Python Developer\'s Guide</a>.</li>\n<li>To contribute to the official <a class="reference" href="doc/">Python documentation</a>, write to\n<a class="reference" href="mailto:docs@python.org">docs@python.org</a>, or use the <a class="reference" href="http://sourceforge.net/tracker/?group_id=5470&atid=305470">Patch Manger</a> to\ncontribute a documentation patch.</li>\n<li>To announce your module or application to the Python community,\nuse <a class="reference" href="news:comp.lang.python.announce">comp.lang.python.announce</a> (or via\nemail, <a class="reference" href="mailto:python-announce@python.org">python-announce@python.org</a>,\nif you lack news access). More info: <a class="reference" href="community/lists.html#clpa">the announcements newsgroup\ndescription</a></li>\n<li>To propose changes to the python core, post your thoughts to\n<a class="reference" href="news:comp.lang.python">comp.lang.python</a>. If you have an\nimplementation, follow the <a class="reference" href="/patches/">Python Patch Guidelines</a>.</li>\n</ul>\n</div>\n<div class="section">\n<h2><a id="did-we-miss-your-concern" name="did-we-miss-your-concern">Did we miss your concern?</a></h2>\n<ul class="simple">\n<li>Contact <a class="reference" href="mailto:webmaster@python.org">webmaster@python.org</a> and let us\nknow how we can help!</li>\n</ul>\n</div>\n</div>\n' 1374 1374 tRp543 1375 1375 sssg44 … … 1569 1569 (dp626 1570 1570 g287 1571 (lp627 1572 (dp628 1573 g37 1574 g290 1575 sg39 1571 g288 1572 sg289 1573 (dp627 1576 1574 g291 1577 sa(dp629 1578 g37 1579 g293 1580 sg39 1575 g292 1576 sg293 1581 1577 g294 1582 sasg295 1583 (dp630 1584 g297 1585 g298 1586 sg299 1587 g300 1588 ssg301 1578 ssg295 1589 1579 (ipyramid.yamlRegistry 1590 1580 fragmentFile 1591 p6 311592 (dp6 321581 p628 1582 (dp629 1593 1583 g23 1594 1584 g49 1595 sbsg304 1585 sbsg298 1586 (lp630 1587 (dp631 1588 g37 1589 g301 1590 sg39 1591 g302 1592 sa(dp632 1593 g37 1594 g304 1595 sg39 1596 1596 g305 1597 s sg271597 sassg27 1598 1598 (dp633 1599 1599 S'content' … … 1636 1636 (g32 1637 1637 g6 1638 S'<div class="section" id="python-for-windows-95-98-nt-2000-me-xp">\n<h1><a name="python-for-windows-95-98-nt-2000-me-xp">Python for Windows 95, 98, NT, 2000, ME, XP</a></h1>\n<p>For many years, Python releases have included an excellent Windows\ninstaller. See the <a class="reference" href="./">individual releases</a> for details.</p>\n<p>Users of Python 2.2.1 and earlier may want to download a new\n<a class="reference" href="http://www.python.org/ftp/python/2.2.1/UNWISE.EXE">UNWISE.EXE</a>\nfrom Wise that fixes a bug which could cause the uninstaller to\ndisappear in some circumstances. Just drop it over the old uninstaller,\nwhich will be at C:Python22UNWISE.EXE unless you chose a different\ndirectory at install time.</p>\n<p>Win32all, Mark Hammond\'s add-on for the regular Python installer (also\nincluding the Win32 API, COM support, and Pythonwin), is available from the\n<a class="reference" href="http://sourceforge.net/projects/pywin32/">pywin32 project</a> on\nSourceForge.</p>\n</div>\n<div class="section" id="python-for-alpha-nt">\n<h1><a name="python-for-alpha-nt">Python for Alpha/NT</a></h1>\n<p>There\'s a Python 1.5.2 binary for Windows NT on DEC Alpha\nworkstations on <a class="reference" href="http://www.alphant.com">www.alphant.com</a>\n(in the Programming category of the File Archives).</p>\n</div>\n<div class="section" id="python-for-windows-ce">\n<h1><a name="python-for-windows-ce">Python for Windows CE</a></h1>\n<p>Mark Hammond once ported Python 1.5.2 to Windows CE. This is still\navailable from <a class="reference" href="http://starship.python.net/crew/mhammond/ce/old.html">Mark\'s Windows CE pages on Starship</a>.</p>\n<p>More recently, there is an active <a class="reference" href="http://mail.python.org/mailman/listinfo/pythonce">PythonCE list</a>. This list has migrated from a yahoo groups list, the <a class="reference" href="http://groups.yahoo.com/group/python-ce/">archives there</a> may\nstill be of use.</p>\n<p>There is a <a class="reference" href="http://www.murkworks.com/Research/Python/PocketPCPython/Overview">StrongArm WinCE binary of Python 2.2</a> available.</p>\n<p><a class="reference" href="http://sourceforge.net/projects/pythonce">The PythonCE project on Sourceforge</a> has binaries of 2.3.4 for StrongArm available.</p>\n</div>\n<div class="section" id="python-for-dos">\n<h1><aname="python-for-dos">Python for DOS</a></h1>\n<p><a class="reference" href="http://members.lycos.co.uk/bdeck/">Python 2.2.1 for DOS/DPMI</a> is now available (built on the DJGPP platform).</p>\n</div>\n'1638 S'<div class="section">\n<h1><a id="python-for-windows-95-98-nt-2000-me-xp" name="python-for-windows-95-98-nt-2000-me-xp">Python for Windows 95, 98, NT, 2000, ME, XP</a></h1>\n<p>For many years, Python releases have included an excellent Windows\ninstaller. See the <a class="reference" href="./">individual releases</a> for details.</p>\n<p>Users of Python 2.2.1 and earlier may want to download a new\n<a class="reference" href="http://www.python.org/ftp/python/2.2.1/UNWISE.EXE">UNWISE.EXE</a>\nfrom Wise that fixes a bug which could cause the uninstaller to\ndisappear in some circumstances. Just drop it over the old uninstaller,\nwhich will be at C:Python22UNWISE.EXE unless you chose a different\ndirectory at install time.</p>\n<p>Win32all, Mark Hammond\'s add-on for the regular Python installer (also\nincluding the Win32 API, COM support, and Pythonwin), is available from the\n<a class="reference" href="http://sourceforge.net/projects/pywin32/">pywin32 project</a> on\nSourceForge.</p>\n</div>\n<div class="section">\n<h1><a id="python-for-alpha-nt" name="python-for-alpha-nt">Python for Alpha/NT</a></h1>\n<p>There\'s a Python 1.5.2 binary for Windows NT on DEC Alpha\nworkstations on <a class="reference" href="http://www.alphant.com">www.alphant.com</a>\n(in the Programming category of the File Archives).</p>\n</div>\n<div class="section">\n<h1><a id="python-for-windows-ce" name="python-for-windows-ce">Python for Windows CE</a></h1>\n<p>Mark Hammond once ported Python 1.5.2 to Windows CE. This is still\navailable from <a class="reference" href="http://starship.python.net/crew/mhammond/ce/old.html">Mark\'s Windows CE pages on Starship</a>.</p>\n<p>More recently, there is an active <a class="reference" href="http://mail.python.org/mailman/listinfo/pythonce">PythonCE list</a>. This list has migrated from a yahoo groups list, the <a class="reference" href="http://groups.yahoo.com/group/python-ce/">archives there</a> may\nstill be of use.</p>\n<p>There is a <a class="reference" href="http://www.murkworks.com/Research/Python/PocketPCPython/Overview">StrongArm WinCE binary of Python 2.2</a> available.</p>\n<p><a class="reference" href="http://sourceforge.net/projects/pythonce">The PythonCE project on Sourceforge</a> has binaries of 2.3.4 for StrongArm available.</p>\n</div>\n<div class="section">\n<h1><a id="python-for-dos" name="python-for-dos">Python for DOS</a></h1>\n<p><a class="reference" href="http://members.lycos.co.uk/bdeck/">Python 2.2.1 for DOS/DPMI</a> is now available (built on the DJGPP platform).</p>\n</div>\n' 1639 1639 tRp651 1640 1640 sS'breadcrumb' … … 2023 2023 (dp808 2024 2024 g287 2025 (lp809 2026 (dp810 2027 g37 2028 g290 2029 sg39 2025 g288 2026 sg289 2027 (dp809 2030 2028 g291 2031 sa(dp811 2032 g37 2033 g293 2034 sg39 2029 g292 2030 sg293 2035 2031 g294 2036 sasg295 2037 (dp812 2038 g297 2039 g298 2040 sg299 2041 g300 2042 ssg301 2032 ssg295 2043 2033 (ipyramid.yamlRegistry 2044 2034 fragmentFile 2045 p81 32046 (dp81 42035 p810 2036 (dp811 2047 2037 g23 2048 2038 g49 2049 sbsg304 2039 sbsg298 2040 (lp812 2041 (dp813 2042 g37 2043 g301 2044 sg39 2045 g302 2046 sa(dp814 2047 g37 2048 g304 2049 sg39 2050 2050 g305 2051 s sg272051 sassg27 2052 2052 (dp815 2053 2053 S'content' … … 2090 2090 (g32 2091 2091 g6 2092 S'<div class="section" id="python-1-5-2">\n<h1><a name="python-1-5-2">Python 1.5.2</a></h1>\n<blockquote>\n<strong>Do yourself a favor</strong> and get a <a class="reference" href="../download/">more recent version</a>!</blockquote>\n<p>On 13 April 1999, the final version of Python 1.5.2 was released:</p>\n<ul class="simple">\n<li><a class="reference" href="../ftp/python/src/py152.tgz">Python 1.5.2 sources</a> (2.5 MB)</li>\n<li><a class="reference" href="../ftp/python/win32/py152.exe">Python 1.5.2 installer for Windows</a> (5.0 MB)</li>\n<li><a class="reference" href="NEWS-152.txt">What\'s new in 1.5.2?</a></li>\n<li><a class="reference" href="../doc/1.5.2p2/">Documentation</a> (both online and downloadable)</li>\n</ul>\n<p>Note: the Python installer for Windows includes the Tcl/Tk 8.0.5\ninstaller. See the <a class="reference" href="../topics/tkinter/trouble.html#win">Tkinter resource guide</a>\nfor troubleshooting the Tcl/Tk installation.</p>\n<p>Windows users may also be interested in Mark Hammond\'s <a class="reference" href="http://starship.python.net/crew/mhammond/">win32all</a>, a collection of Windows-specific extensions including\nCOM support and Pythonwin, an IDE built using Windows components.</p>\n</div>\n<div class="section" id="if-you-find-a-bug">\n<h1><aname="if-you-find-a-bug">If You Find a Bug</a></h1>\n<p>It was probably already fixed in a later version. Please try the\n<a class="reference" href="../download/">latest version</a> before <a class="reference" href="http://sourceforge.net/bugs/?group_id=5470">reporting bugs</a>.</p>\n</div>\n'2092 S'<div class="section">\n<h1><a id="python-1-5-2" name="python-1-5-2">Python 1.5.2</a></h1>\n<blockquote>\n<strong>Do yourself a favor</strong> and get a <a class="reference" href="../download/">more recent version</a>!</blockquote>\n<p>On 13 April 1999, the final version of Python 1.5.2 was released:</p>\n<ul class="simple">\n<li><a class="reference" href="../ftp/python/src/py152.tgz">Python 1.5.2 sources</a> (2.5 MB)</li>\n<li><a class="reference" href="../ftp/python/win32/py152.exe">Python 1.5.2 installer for Windows</a> (5.0 MB)</li>\n<li><a class="reference" href="NEWS-152.txt">What\'s new in 1.5.2?</a></li>\n<li><a class="reference" href="../doc/1.5.2p2/">Documentation</a> (both online and downloadable)</li>\n</ul>\n<p>Note: the Python installer for Windows includes the Tcl/Tk 8.0.5\ninstaller. See the <a class="reference" href="../topics/tkinter/trouble.html#win">Tkinter resource guide</a>\nfor troubleshooting the Tcl/Tk installation.</p>\n<p>Windows users may also be interested in Mark Hammond\'s <a class="reference" href="http://starship.python.net/crew/mhammond/">win32all</a>, a collection of Windows-specific extensions including\nCOM support and Pythonwin, an IDE built using Windows components.</p>\n</div>\n<div class="section">\n<h1><a id="if-you-find-a-bug" name="if-you-find-a-bug">If You Find a Bug</a></h1>\n<p>It was probably already fixed in a later version. Please try the\n<a class="reference" href="../download/">latest version</a> before <a class="reference" href="http://sourceforge.net/bugs/?group_id=5470">reporting bugs</a>.</p>\n</div>\n' 2093 2093 tRp833 2094 2094 sS'breadcrumb' … … 2647 2647 (dp1031 2648 2648 g287 2649 (lp1032 2650 (dp1033 2651 g37 2652 g290 2653 sg39 2649 g288 2650 sg289 2651 (dp1032 2654 2652 g291 2655 sa(dp1034 2656 g37 2657 g293 2658 sg39 2653 g292 2654 sg293 2659 2655 g294 2660 sasg295 2661 (dp1035 2662 g297 2663 g298 2664 sg299 2665 g300 2666 ssg301 2656 ssg295 2667 2657 (ipyramid.yamlRegistry 2668 2658 fragmentFile 2669 p103 62670 (dp103 72659 p1033 2660 (dp1034 2671 2661 g23 2672 2662 g49 2673 sbsg304 2663 sbsg298 2664 (lp1035 2665 (dp1036 2666 g37 2667 g301 2668 sg39 2669 g302 2670 sa(dp1037 2671 g37 2672 g304 2673 sg39 2674 2674 g305 2675 s sg272675 sassg27 2676 2676 (dp1038 2677 2677 S'content' … … 2714 2714 (g32 2715 2715 g6 2716 S'<div class="section" id="openpgp-public-keys">\n<h1><aname="openpgp-public-keys">OpenPGP Public Keys</a></h1>\n<p>OpenPGP Public Keys are available to <a class="reference" href="/download/pubkeys/pubkeys.txt">download</a>.</p>\n</div>\n'2716 S'<div class="section">\n<h1><a id="openpgp-public-keys" name="openpgp-public-keys">OpenPGP Public Keys</a></h1>\n<p>OpenPGP Public Keys are available to <a class="reference" href="/download/pubkeys/pubkeys.txt">download</a>.</p>\n</div>\n' 2717 2717 tRp1056 2718 2718 sS'breadcrumb' … … 3057 3057 (dp1169 3058 3058 g287 3059 (lp1170 3060 (dp1171 3061 g37 3062 g290 3063 sg39 3059 g288 3060 sg289 3061 (dp1170 3064 3062 g291 3065 sa(dp1172 3066 g37 3067 g293 3068 sg39 3063 g292 3064 sg293 3069 3065 g294 3070 sasg295 3071 (dp1173 3072 g297 3073 g298 3074 sg299 3075 g300 3076 ssg301 3066 ssg295 3077 3067 (ipyramid.yamlRegistry 3078 3068 fragmentFile 3079 p117 43080 (dp117 53069 p1171 3070 (dp1172 3081 3071 g23 3082 3072 g49 3083 sbsg304 3073 sbsg298 3074 (lp1173 3075 (dp1174 3076 g37 3077 g301 3078 sg39 3079 g302 3080 sa(dp1175 3081 g37 3082 g304 3083 sg39 3084 3084 g305 3085 s sg273085 sassg27 3086 3086 (dp1176 3087 3087 S'content' … … 3124 3124 (g32 3125 3125 g6 3126 S'<div class="section" id="the-python-community">\n<h1><aname="the-python-community">The Python Community</a></h1>\n<p>The only thing more fun than programming in Python is exchanging\ninformation and ideas with other Python users. The Python community\ninteracts in many different forums, both online and in the real world.</p>\n<ul class="simple">\n<li><a class="reference" href="/community/lists">Mailing Lists and Newsgroups</a></li>\n<li><a class="reference" href="/community/sigs">SIGS</a></li>\n<li><a class="reference" href="/community/irc">Internet Relay Chat (IRC)</a></li>\n<li><a class="reference" href="/community/logos">Logos</a></li>\n</ul>\n<p><a class="reference" href="http://www.python.org/moin/LocalUserGroups">A listing of local user groups</a>\nand <a class="reference" href="http://www.python.org/moin/PythonEvents">a calendar of events</a>\nare maintained in the Python Wiki.</p>\n<p>In addition to user groups, there are three large conferences each\nyear where the Python community gathers together:</p>\n<ul class="simple">\n<li><a class="reference" href="/community/pycon">PyCon</a></li>\n<li><a class="reference" href="/community/europython">EuroPython</a></li>\n<li><a class="reference" href="http://conferences.oreilly.com/oscon/">OSCON/IPC (O\'Reilly Open Source Convention / International Python Conference)</a></li>\n</ul>\n<p>These conference pages often tend to lag behind until the next\nconference starts gearing up. You can see the history of previous\nconferences on the <a class="reference" href="workshops">conferences and workshops page</a></p>\n</div>\n'3126 S'<div class="section">\n<h1><a id="the-python-community" name="the-python-community">The Python Community</a></h1>\n<p>The only thing more fun than programming in Python is exchanging\ninformation and ideas with other Python users. The Python community\ninteracts in many different forums, both online and in the real world.</p>\n<ul class="simple">\n<li><a class="reference" href="/community/lists">Mailing Lists and Newsgroups</a></li>\n<li><a class="reference" href="/community/sigs">SIGS</a></li>\n<li><a class="reference" href="/community/irc">Internet Relay Chat (IRC)</a></li>\n<li><a class="reference" href="/community/logos">Logos</a></li>\n</ul>\n<p><a class="reference" href="http://www.python.org/moin/LocalUserGroups">A listing of local user groups</a>\nand <a class="reference" href="http://www.python.org/moin/PythonEvents">a calendar of events</a>\nare maintained in the Python Wiki.</p>\n<p>In addition to user groups, there are three large conferences each\nyear where the Python community gathers together:</p>\n<ul class="simple">\n<li><a class="reference" href="/community/pycon">PyCon</a></li>\n<li><a class="reference" href="/community/europython">EuroPython</a></li>\n<li><a class="reference" href="http://conferences.oreilly.com/oscon/">OSCON/IPC (O\'Reilly Open Source Convention / International Python Conference)</a></li>\n</ul>\n<p>These conference pages often tend to lag behind until the next\nconference starts gearing up. You can see the history of previous\nconferences on the <a class="reference" href="workshops">conferences and workshops page</a></p>\n</div>\n' 3127 3127 tRp1194 3128 3128 sS'breadcrumb' … … 3402 3402 (dp1303 3403 3403 g287 3404 (lp1304 3405 (dp1305 3406 g37 3407 g290 3408 sg39 3404 g288 3405 sg289 3406 (dp1304 3409 3407 g291 3410 sa(dp1306 3411 g37 3412 g293 3413 sg39 3408 g292 3409 sg293 3414 3410 g294 3415 sasg295 3416 (dp1307 3417 g297 3418 g298 3419 sg299 3420 g300 3421 ssg301 3411 ssg295 3422 3412 (ipyramid.yamlRegistry 3423 3413 fragmentFile 3424 p130 83425 (dp130 93414 p1305 3415 (dp1306 3426 3416 g23 3427 3417 g49 3428 sbsg304 3418 sbsg298 3419 (lp1307 3420 (dp1308 3421 g37 3422 g301 3423 sg39 3424 g302 3425 sa(dp1309 3426 g37 3427 g304 3428 sg39 3429 3429 g305 3430 s sg273430 sassg27 3431 3431 (dp1310 3432 3432 S'content' … … 3469 3469 (g32 3470 3470 g6 3471 S'<div class="section" id="python-org-maintainence-and-administration">\n<h1><aname="python-org-maintainence-and-administration">Python.org Maintainence and Administration</a></h1>\n<p>This area contained information on how to update the python.org website and linked to the following other pages:</p>\n<ul class="simple">\n<li>Style Guide</li>\n<li>Translators\' Guide</li>\n<li>404 Report</li>\n</ul>\n<p>This information has not been repeated here as the process has changed in the new website. This section now needs updating.</p>\n</div>\n'3471 S'<div class="section">\n<h1><a id="python-org-maintainence-and-administration" name="python-org-maintainence-and-administration">Python.org Maintainence and Administration</a></h1>\n<p>This area contained information on how to update the python.org website and linked to the following other pages:</p>\n<ul class="simple">\n<li>Style Guide</li>\n<li>Translators\' Guide</li>\n<li>404 Report</li>\n</ul>\n<p>This information has not been repeated here as the process has changed in the new website. This section now needs updating.</p>\n</div>\n' 3472 3472 tRp1328 3473 3473 sS'breadcrumb' … … 3915 3915 (dp1476 3916 3916 g287 3917 (lp1477 3918 (dp1478 3919 g37 3920 g290 3921 sg39 3917 g288 3918 sg289 3919 (dp1477 3922 3920 g291 3923 sa(dp1479 3924 g37 3925 g293 3926 sg39 3921 g292 3922 sg293 3927 3923 g294 3928 sasg295 3929 (dp1480 3930 g297 3931 g298 3932 sg299 3933 g300 3934 ssg301 3924 ssg295 3935 3925 (ipyramid.yamlRegistry 3936 3926 fragmentFile 3937 p14 813938 (dp14 823927 p1478 3928 (dp1479 3939 3929 g23 3940 3930 g49 3941 sbsg304 3931 sbsg298 3932 (lp1480 3933 (dp1481 3934 g37 3935 g301 3936 sg39 3937 g302 3938 sa(dp1482 3939 g37 3940 g304 3941 sg39 3942 3942 g305 3943 s sg273943 sassg27 3944 3944 (dp1483 3945 3945 S'content' … … 3982 3982 (g32 3983 3983 g6 3984 S'<div class="section" id="contributed-python-software">\n<h1><a name="contributed-python-software">Contributed Python Software</a></h1>\n<p><a class="reference" href="ahref="http://www.vex.net/parnassus/vop-feedback.py"">Tim Middleton</a> manages the <a class="reference" href="http://www.vex.net/parnassus/">Vaults of Parnassus: Python Resources</a>, a very cool repository of Python software. We are encouraging everyone writing or looking for third-party Python software to use Parnassus.</p>\n<div class="section" id="how-to-contribute-python-software">\n<h2><a name="how-to-contribute-python-software">How to Contribute Python Software</a></h2>\n<p>You write some cool Python module or application, and you\'d like to make it available to the wider Python community. How do you go about doing this? Below are some general guidelines on what you should do to package, register, and announce your software.</p>\n<p>If you wish to contribute a patch or improvement to Python, you should consult the <a class="reference" href="../dev/">Python Developer\'s Guide</a>.</p>\n<ul>\n<li><dl class="first docutils">\n<dt><strong>Create your distribution.</strong></dt>\n<dd><p class="first last">Do yourself a favor, and check out the <a class="reference" href="../doc/current/dist/dist.html">distutils</a> package.</p>\n</dd>\n</dl>\n</li>\n<li><dl class="first docutils">\n<dt><strong>Make your package available.</strong></dt>\n<dd><p class="first last">Next, you need to make your package available on the net some\nwhere. The best thing to do is to put your package on your own\nWeb or FTP site. If you don\'t have such a site readily available,\nyou might consider getting one of those free Web accounts that\nseem to be all over the place these days. Any of these should be\nadequate for disseminating small Python packages.</p>\n</dd>\n</dl>\n</li>\n<li><dl class="first docutils">\n<dt><strong>Register your package.</strong></dt>\n<dd><p class="first last">Once your stuff is available on the net, you\'ll want to register\nit with <a class="reference" href="http://www.vex.net/parnassus/">The Vaults of Parnassus</a>. We\'d like to see Parnassus become the\ncentral registry of all Python contributed software, so you should\ndefinitely register your software there. If you\'re looking for\nPython software, Parnassus should be your first stop!</p>\n</dd>\n</dl>\n</li>\n<li><dl class="first docutils">\n<dt><strong>Make an announcement.</strong></dt>\n<dd><p class="first last">Finally, you\'ll want to announce your software to the Python\nworld! The best way to do this is to send an email to\n<a class="reference" href="mailto:python-announce@python.org">python-announce@python.org</a> \ndescribing your software. See <a class="reference" href="#pyann">below for posting guidelines</a>. You might also want to post the same announcement\nto the general Python list\n<a class="reference" href="mailto:python-list@python.org">python-list@python.org</a>\n(mirrored as the Usenet newsgroup\n<a class="reference" href="news:comp.lang.python">comp.lang.python</a>).</p>\n</dd>\n</dl>\n</li>\n<li><p class="first"><strong>Sit back and await your fame.</strong></p>\n</li>\n</ul>\n</div>\n<div class="section" id="python-announce-mailing-list-guidelines">\n<h2><aname="python-announce-mailing-list-guidelines">Python-announce mailing list guidelines</a></h2>\n<p>Here is the\n<a class="reference" href="ftp://rtfm.mit.edu/pub/usenet/comp.lang.python.announce/python-newsgroup-faq">comp.lang.python.announce posting guidelines</a> (A.K.A. the c.l.py.a FAQ). These are posted bi-weekly to the\n<a class="reference" href="news:comp.lang.python">comp.lang.python</a>,\n<a class="reference" href="news:comp.lang.python.announce">comp.lang.python.announce</a>,\n<a class="reference" href="news:comp.answers">comp.answers</a>, and\n<a class="reference" href="news:news.answers">news.answers</a> newsgroups. Your\nannouncement will be parsed by automated scripts which update other\nlists of recent Python news, so failure to follow the guidelines may\nprevent your announcement from reaching the whole Python community.</p>\n</div>\n</div>\n'3984 S'<div class="section">\n<h1><a id="contributed-python-software" name="contributed-python-software">Contributed Python Software</a></h1>\n<p><a class="reference" href="ahref="http://www.vex.net/parnassus/vop-feedback.py"">Tim Middleton</a> manages the <a class="reference" href="http://www.vex.net/parnassus/">Vaults of Parnassus: Python Resources</a>, a very cool repository of Python software. We are encouraging everyone writing or looking for third-party Python software to use Parnassus.</p>\n<div class="section">\n<h2><a id="how-to-contribute-python-software" name="how-to-contribute-python-software">How to Contribute Python Software</a></h2>\n<p>You write some cool Python module or application, and you\'d like to make it available to the wider Python community. How do you go about doing this? Below are some general guidelines on what you should do to package, register, and announce your software.</p>\n<p>If you wish to contribute a patch or improvement to Python, you should consult the <a class="reference" href="../dev/">Python Developer\'s Guide</a>.</p>\n<ul>\n<li><dl class="first docutils">\n<dt><strong>Create your distribution.</strong></dt>\n<dd><p class="first last">Do yourself a favor, and check out the <a class="reference" href="../doc/current/dist/dist.html">distutils</a> package.</p>\n</dd>\n</dl>\n</li>\n<li><dl class="first docutils">\n<dt><strong>Make your package available.</strong></dt>\n<dd><p class="first last">Next, you need to make your package available on the net some\nwhere. The best thing to do is to put your package on your own\nWeb or FTP site. If you don\'t have such a site readily available,\nyou might consider getting one of those free Web accounts that\nseem to be all over the place these days. Any of these should be\nadequate for disseminating small Python packages.</p>\n</dd>\n</dl>\n</li>\n<li><dl class="first docutils">\n<dt><strong>Register your package.</strong></dt>\n<dd><p class="first last">Once your stuff is available on the net, you\'ll want to register\nit with <a class="reference" href="http://www.vex.net/parnassus/">The Vaults of Parnassus</a>. We\'d like to see Parnassus become the\ncentral registry of all Python contributed software, so you should\ndefinitely register your software there. If you\'re looking for\nPython software, Parnassus should be your first stop!</p>\n</dd>\n</dl>\n</li>\n<li><dl class="first docutils">\n<dt><strong>Make an announcement.</strong></dt>\n<dd><p class="first last">Finally, you\'ll want to announce your software to the Python\nworld! The best way to do this is to send an email to\n<a class="reference" href="mailto:python-announce@python.org">python-announce@python.org</a>\ndescribing your software. See <a class="reference" href="#pyann">below for posting guidelines</a>. You might also want to post the same announcement\nto the general Python list\n<a class="reference" href="mailto:python-list@python.org">python-list@python.org</a>\n(mirrored as the Usenet newsgroup\n<a class="reference" href="news:comp.lang.python">comp.lang.python</a>).</p>\n</dd>\n</dl>\n</li>\n<li><p class="first"><strong>Sit back and await your fame.</strong></p>\n</li>\n</ul>\n</div>\n<div class="section">\n<h2><a id="python-announce-mailing-list-guidelines" name="python-announce-mailing-list-guidelines">Python-announce mailing list guidelines</a></h2>\n<p>Here is the\n<a class="reference" href="ftp://rtfm.mit.edu/pub/usenet/comp.lang.python.announce/python-newsgroup-faq">comp.lang.python.announce posting guidelines</a> (A.K.A. the c.l.py.a FAQ). These are posted bi-weekly to the\n<a class="reference" href="news:comp.lang.python">comp.lang.python</a>,\n<a class="reference" href="news:comp.lang.python.announce">comp.lang.python.announce</a>,\n<a class="reference" href="news:comp.answers">comp.answers</a>, and\n<a class="reference" href="news:news.answers">news.answers</a> newsgroups. Your\nannouncement will be parsed by automated scripts which update other\nlists of recent Python news, so failure to follow the guidelines may\nprevent your announcement from reaching the whole Python community.</p>\n</div>\n</div>\n' 3985 3985 tRp1501 3986 3986 sS'breadcrumb' … … 4349 4349 (dp1624 4350 4350 g287 4351 (lp1625 4352 (dp1626 4353 g37 4354 g290 4355 sg39 4351 g288 4352 sg289 4353 (dp1625 4356 4354 g291 4357 sa(dp1627 4358 g37 4359 g293 4360 sg39 4355 g292 4356 sg293 4361 4357 g294 4362 sasg295 4363 (dp1628 4364 g297 4365 g298 4366 sg299 4367 g300 4368 ssg301 4358 ssg295 4369 4359 (ipyramid.yamlRegistry 4370 4360 fragmentFile 4371 p162 94372 (dp16 304361 p1626 4362 (dp1627 4373 4363 g23 4374 4364 g49 4375 sbsg304 4365 sbsg298 4366 (lp1628 4367 (dp1629 4368 g37 4369 g301 4370 sg39 4371 g302 4372 sa(dp1630 4373 g37 4374 g304 4375 sg39 4376 4376 g305 4377 s sg274377 sassg27 4378 4378 (dp1631 4379 4379 S'content' … … 4416 4416 (g32 4417 4417 g6 4418 S'<div class="section" id="database-topic-guide">\n<h1><aname="database-topic-guide">Database Topic Guide</a></h1>\n<p>This Topic Guide covers accessing relational databases from Python.\nThe related issue of adding persistence to Python objects is also\ndiscussed. Links to relevant Python modules, documentation, and\nprojects are provided.</p>\n<ul class="simple">\n<li><a class="reference" href="/peps/pep-0249.html">DB-API spec v2.0</a> Version 2.0 of an API specification for connecting to databases from Python.</li>\n<li><a class="reference" href="/peps/pep-0248.html">DB-API spec v1.0</a> Version 1.0 of the API specification.</li>\n<li><a class="reference" href="modules.html">Database Modules</a> Database modules that implement the DB-API specification.</li>\n<li><a class="reference" href="docs.html">Documentation</a> Related documents and articles</li>\n<li><a class="reference" href="other-db.html">Other Database Modules</a> Older database modules that <strong>do not</strong> implement the DB-API specification.</li>\n<li><a class="reference" href="persistence.html">Persistence</a> Other mechanisms for implementing persistent Python objects.</li>\n<li><a class="reference" href="books.html">Database Books</a> A list of books useful for learning about database programming and SQL.</li>\n<li><a class="reference" href="../../sigs/db-sig/">Database SIG</a> The Database Special Interest Group</li>\n</ul>\n</div>\n'4418 S'<div class="section">\n<h1><a id="database-topic-guide" name="database-topic-guide">Database Topic Guide</a></h1>\n<p>This Topic Guide covers accessing relational databases from Python.\nThe related issue of adding persistence to Python objects is also\ndiscussed. Links to relevant Python modules, documentation, and\nprojects are provided.</p>\n<ul class="simple">\n<li><a class="reference" href="/peps/pep-0249.html">DB-API spec v2.0</a> Version 2.0 of an API specification for connecting to databases from Python.</li>\n<li><a class="reference" href="/peps/pep-0248.html">DB-API spec v1.0</a> Version 1.0 of the API specification.</li>\n<li><a class="reference" href="modules.html">Database Modules</a> Database modules that implement the DB-API specification.</li>\n<li><a class="reference" href="docs.html">Documentation</a> Related documents and articles</li>\n<li><a class="reference" href="other-db.html">Other Database Modules</a> Older database modules that <strong>do not</strong> implement the DB-API specification.</li>\n<li><a class="reference" href="persistence.html">Persistence</a> Other mechanisms for implementing persistent Python objects.</li>\n<li><a class="reference" href="books.html">Database Books</a> A list of books useful for learning about database programming and SQL.</li>\n<li><a class="reference" href="../../sigs/db-sig/">Database SIG</a> The Database Special Interest Group</li>\n</ul>\n</div>\n' 4419 4419 tRp1649 4420 4420 sS'breadcrumb' … … 5051 5051 (dp1907 5052 5052 g287 5053 (lp1908 5054 (dp1909 5055 g37 5056 g290 5057 sg39 5053 g288 5054 sg289 5055 (dp1908 5058 5056 g291 5059 sa(dp1910 5060 g37 5061 g293 5062 sg39 5057 g292 5058 sg293 5063 5059 g294 5064 sasg295 5065 (dp1911 5066 g297 5067 g298 5068 sg299 5069 g300 5070 ssg301 5060 ssg295 5071 5061 (ipyramid.yamlRegistry 5072 5062 fragmentFile 5073 p19 125074 (dp191 35063 p1909 5064 (dp1910 5075 5065 g23 5076 5066 g49 5077 sbsg304 5067 sbsg298 5068 (lp1911 5069 (dp1912 5070 g37 5071 g301 5072 sg39 5073 g302 5074 sa(dp1913 5075 g37 5076 g304 5077 sg39 5078 5078 g305 5079 s sg275079 sassg27 5080 5080 (dp1914 5081 5081 S'content' … … 5118 5118 (g32 5119 5119 g6 5120 S'<div class="section" id="python-topic-guides">\n<h1><a name="python-topic-guides">Python Topic Guides</a></h1>\n<p>Python Topic Guides provide overviews of Python resources associated\nwith specific topics. They are produced by volunteers\ninterested in making those resources easier for everyone to\nfind.</p>\n<blockquote>\n<ul class="simple">\n<li><a class="reference" href="http://www.python.org/moin/BeginnersGuide">Beginner\'s Guide</a> - Help for the beginning programmer</li>\n<li><a class="reference" href="database/">Databases</a> - About interfacing with\nexternal databases</li>\n<li><a class="reference" href="http://www.python.org/moin/LanguageParsing">Parser Generators</a> - Generating Python lexers and parsers.</li>\n<li><a class="reference" href="http://www.python.org/moin/NumericAndScientific">Scientific Computing</a> - Numeric\nPython, Symbolic Computing, Data Plotting, etc.</li>\n<li><a class="reference" href="http://www.python.org/moin/TkInter">Tkinter</a> - Python\'s de-facto GUI\nstandard (based on Tcl/Tk)</li>\n<li><a class="reference" href="web/">Web Programming</a> - General guide to\nWeb-related programming with Python</li>\n<li><a class="reference" href="http://pyxml.sourceforge.net/topics/">XML</a> - eXtensible Markup Language processing</li>\n</ul>\n</blockquote>\n<div class="section" id="year-end-summaries">\n<h2><a name="year-end-summaries">Year-end Summaries</a></h2>\n<p>These reports summarize the Python community\'s activities\nfor a given year.</p>\n<blockquote>\n<ul class="simple">\n<li><a class="reference" href="yisl2002.html">2002</a> -- also includes Lua, Perl, Ruby, Tcl summaries.</li>\n<li><a class="reference" href="2003.html">2003</a></li>\n</ul>\n</blockquote>\n</div>\n</div>\n'5120 S'<div class="section">\n<h1><a id="python-topic-guides" name="python-topic-guides">Python Topic Guides</a></h1>\n<p>Python Topic Guides provide overviews of Python resources associated\nwith specific topics. They are produced by volunteers\ninterested in making those resources easier for everyone to\nfind.</p>\n<blockquote>\n<ul class="simple">\n<li><a class="reference" href="http://www.python.org/moin/BeginnersGuide">Beginner\'s Guide</a> - Help for the beginning programmer</li>\n<li><a class="reference" href="database/">Databases</a> - About interfacing with\nexternal databases</li>\n<li><a class="reference" href="http://www.python.org/moin/LanguageParsing">Parser Generators</a> - Generating Python lexers and parsers.</li>\n<li><a class="reference" href="http://www.python.org/moin/NumericAndScientific">Scientific Computing</a> - Numeric\nPython, Symbolic Computing, Data Plotting, etc.</li>\n<li><a class="reference" href="http://www.python.org/moin/TkInter">Tkinter</a> - Python\'s de-facto GUI\nstandard (based on Tcl/Tk)</li>\n<li><a class="reference" href="web/">Web Programming</a> - General guide to\nWeb-related programming with Python</li>\n<li><a class="reference" href="http://pyxml.sourceforge.net/topics/">XML</a> - eXtensible Markup Language processing</li>\n</ul>\n</blockquote>\n<div class="section">\n<h2><a id="year-end-summaries" name="year-end-summaries">Year-end Summaries</a></h2>\n<p>These reports summarize the Python community\'s activities\nfor a given year.</p>\n<blockquote>\n<ul class="simple">\n<li><a class="reference" href="yisl2002.html">2002</a> -- also includes Lua, Perl, Ruby, Tcl summaries.</li>\n<li><a class="reference" href="2003.html">2003</a></li>\n</ul>\n</blockquote>\n</div>\n</div>\n' 5121 5121 tRp1932 5122 5122 sS'breadcrumb' … … 5660 5660 (dp2103 5661 5661 g287 5662 (lp2104 5663 (dp2105 5664 g37 5665 g290 5666 sg39 5662 g288 5663 sg289 5664 (dp2104 5667 5665 g291 5668 sa(dp2106 5669 g37 5670 g293 5671 sg39 5666 g292 5667 sg293 5672 5668 g294 5673 sasg295 5674 (dp2107 5675 g297 5676 g298 5677 sg299 5678 g300 5679 ssg301 5669 ssg295 5680 5670 (ipyramid.yamlRegistry 5681 5671 fragmentFile 5682 p210 85683 (dp210 95672 p2105 5673 (dp2106 5684 5674 g23 5685 5675 g49 5686 sbsg304 5676 sbsg298 5677 (lp2107 5678 (dp2108 5679 g37 5680 g301 5681 sg39 5682 g302 5683 sa(dp2109 5684 g37 5685 g304 5686 sg39 5687 5687 g305 5688 s sg275688 sassg27 5689 5689 (dp2110 5690 5690 S'content' … … 5727 5727 (g32 5728 5728 g6 5729 S'<div class="section" id="download-python-software">\n<h1><a name="download-python-software">Download Python Software</a></h1>\n<blockquote>\n<div class="note">\n<p class="first admonition-title">Note</p>\n<p class="last"><strong>Note:</strong> There\'s a <a class="reference" href="/security/PSF-2005-001">security fix</a> for SimpleXMLRPCServer.py in Python 2.2, 2.3, 2.4. Versions before 2.2 are not vulnerable. Of the releases below, only 2.3.5 and 2.4.1 include the fix.</p>\n</div>\n</blockquote>\n<p><a class="reference" href="/download/2.4.1">Python 2.4.1</a> is the current production version of Python. You should start here if you want to learn Python or if you want the most stable version. Here are some quick download links; if you want the MD5 checksums and OpenPGP signatures, look at the <a class="reference" href="/download/2.4.1">Python 2.4.1</a> page:</p>\n<ul class="simple">\n<li><a class="reference" href="/ftp/python/2.4.1/Python-2.4.1.tgz">Python 2.4.1 source</a> (for Unix or OS X compile)</li>\n<li><a class="reference" href="/ftp/python/2.4.1/Python-2.4.1.tar.bz2">Python 2.4.1 source</a> (for Unix or OS X compile, more compressed)</li>\n<li><a class="reference" href="/ftp/python/2.4.1/python-2.4.1.msi">Python 2.4.1 Windows installer</a> (Windows binary -- does not include source)</li>\n<li><a class="reference" href="/ftp/python/2.4/python-2.4.1.ia64.msi">Python 2.4.1 Windows installer</a> (Windows Itanium binary -- does not include source)</li>\n<li><a class="r
