Changeset 118 for branches/timadditionaltypes/pyramid/test/testdata/build_tests/firstpythontest/expected/dev/faq/index.html

Timestamp:

02/04/06 19:29:16 (3 years ago)

Author:

tim

Message:

added new expected data because of updates to docutils I think

Files:

• branches/timadditionaltypes/pyramid/test/testdata/build_tests/firstpythontest/expected/dev/faq/index.html (modified) (30 diffs)

branches/timadditionaltypes/pyramid/test/testdata/build_tests/firstpythontest/expected/dev/faq/index.html

@@ -47 +47 @@
-      
-<div id="breadcrumb"><a href="/dev">python-dev</a> <span class="breadcrumb-separator">&gt;</span> FAQ</div>
- id="frequently-asked-questions-for-developers"
-
+
+id="frequently-asked-questions-for-developers" 
-<table class="docutils field-list" frame="void" rules="none">
-<col class="field-name" />
@@ -61 +61 @@
-</tbody>
-</table>
- id="contents"
-
+
+id="contents" 
-<ul class="auto-toc simple">
-<li><a class="reference" href="#frequently-asked-questions-for-developers" id="id1" name="id1">1&nbsp;&nbsp;&nbsp;Frequently Asked Questions for Developers</a></li>
@@ -122 +122 @@
-</div>
-</div>
- id="general-information"
-
- id="what-is-sourceforge"
-
+
+id="general-information" 
+
+id="what-is-sourceforge" 
-<p>SourceForge is a free hosting service for
-open source projects. The main website is
-found at <a class="reference" href="http://sourceforge.net">http://sourceforge.net</a>.</p>
-</div>
- id="where-can-i-find-python-on-sourceforge"
-
+
+id="where-can-i-find-python-on-sourceforge" 
-<p>The Python project page
-can be found at
-<a class="reference" href="http://sourceforge.net/projects/python">http://sourceforge.net/projects/python</a>.</p>
-</div>
- id="who-is-who-what-is-a-nowonder"
-
+
+id="who-is-who-what-is-a-nowonder" 
-<p>To get the real name, click on &quot;View members&quot; in the &quot;Developer Info&quot;
-box on the SourceForge project page.  This presents a <a class="reference" href="http://sourceforge.net/project/memberlist.php?group_id=5470">list of
@@ -143 +143 @@
-giving their names and SourceForge IDs.</p>
-</div>
- id="how-can-i-become-a-developer"
-
+
+id="how-can-i-become-a-developer" 
-<p>There's only one way to become a developer, and that's through the
-<a class="reference" href="http://mail.python.org/pipermail/python-dev/2002-September/028725.html">School of Hard Knocks</a>.</p>
-</div>
-</div>
- id="cvs"
-
- id="how-do-i-browse-the-cvs-tree-online"
-
+
+id="cvs" 
+
+id="how-do-i-browse-the-cvs-tree-online" 
-<p>If you don't have CVS or you don't want to download the source tree, you can
-browse it using <a class="reference" href="http://www.lyra.org/viewcvs/">ViewCVS</a> at
-<a class="reference" href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python/">http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python/</a>.</p>
-</div>
- id="how-can-i-obtain-a-checkout-of-the-cvs-tree"
-
+
+id="how-can-i-obtain-a-checkout-of-the-cvs-tree" 
-<p>If you are not a SourceForge-recognized Python developer you can check
-out an anonymous CVS version (read-only) of Python:</p>
@@ -187 +187 @@
-to automatically checkout new subdirectories / prune old directories.</p>
-</div>
- id="i-get-the-following-error-message-sorry-you-don-t-have-read-write-access-to-the-history-file"
-
+
+id="i-get-the-following-error-message-sorry-you-don-t-have-read-write-access-to-the-history-file" 
-<p>If you are not a developer, you don't have read/write access. You have to
-check out an anonymous copy. If you are a developer you have to be in the
@@ -201 +201 @@
-up to 6 hours.</p>
-</div>
- id="where-can-i-learn-more-about-cvs"
-
+
+id="where-can-i-learn-more-about-cvs" 
-<p>For SourceForge specific information consult their CVS documentation at
-<a class="reference" href="http://sfdocs.sourceforge.net/sfdocs">http://sfdocs.sourceforge.net/sfdocs</a>.</p>
@@ -208 +208 @@
-<a class="reference" href="http://cvsbook.red-bean.com/cvsbook.html#Introduction">http://cvsbook.red-bean.com/cvsbook.html#Introduction</a>.</p>
-</div>
- id="how-can-i-remove-a-directory-from-the-cvs-tree"
-
+
+id="how-can-i-remove-a-directory-from-the-cvs-tree" 
-<p>Simple answer: You cannot!</p>
-<p>More complicated answer: Remove all files from the directory, delete the
@@ -222 +222 @@
-</pre>
-</div>
- id="how-can-i-revert-changes"
-
+
+id="how-can-i-revert-changes" 
-<p>The fast (and history-friendly) method for backing out a CVS commit is the use
-of the join flag of the update command. You supply the last
@@ -236 +236 @@
-revision 1.16 of ceval.c.</p>
-</div>
- id="how-can-i-view-all-the-log-messages-from-a-specific-point-until-now-on-the-main-trunk-or-a-branch"
-
+
+id="how-can-i-view-all-the-log-messages-from-a-specific-point-until-now-on-the-main-trunk-or-a-branch" 
-<p>When work is being done on a micro release it is often necessary to go back and
-look at the log messages on files from the start of a previous release until now
@@ -281 +281 @@
-branch.</p>
-</div>
- id="how-does-one-view-a-diff-between-two-versions"
-
+
+id="how-does-one-view-a-diff-between-two-versions" 
-<p>Once you have the two revision numbers you wish to generate a diff for (use
-<tt class="docutils literal"><span class="pre">cvs</span> <span class="pre">log</span></tt> if you need help finding which revision numbers you want),
@@ -294 +294 @@
-arbitrary revision number, use only one <tt class="docutils literal"><span class="pre">-r</span></tt> argument.</p>
-</div>
- id="how-can-i-fix-a-log-message-from-a-previous-checkin"
-
+
+id="how-can-i-fix-a-log-message-from-a-previous-checkin" 
-<p>If you happened to do a commit where you feel the need to go back and change the
-log message, you can do so with the <tt class="docutils literal"><span class="pre">cvs</span> <span class="pre">admin</span></tt> command:</p>
@@ -305 +305 @@
-it with.</p>
-</div>
- id="how-do-you-add-a-binary-files"
-
+
+id="how-do-you-add-a-binary-files" 
-<p>You probably want to turn off keyword expansion and line-ending conversion:</p>
-<pre class="literal-block">
@@ -315 +315 @@
-actually makes this work!</p>
-</div>
- id="how-do-you-force-a-branch-tag-on-a-file"
-
+
+id="how-do-you-force-a-branch-tag-on-a-file" 
-<p>The quickest way to force a branch tag branch_tag on a file is to
-issue the command:</p>
@@ -327 +327 @@
-branch which makes the tag a branch tag.</p>
-</div>
- id="how-can-i-check-out-a-tagged-branch"
-
+
+id="how-can-i-check-out-a-tagged-branch" 
-<p>There are two ways to do this.  One uses a pre-existing checkout of the cvs
-tree and the other creates a separate checkout just for the branch.</p>
@@ -336 +336 @@
-cvs update -r branch_tag
-</pre>
-  
+
-Any commits you perform while you are using a tagged branch (which has a
-&quot;sticky bit&quot; set to the tagged branch name) will be performed on the branch.
@@ -363 +363 @@
-updated whenever you updated cvs at a higher directory level.</p>
-</div>
- id="how-do-i-find-out-who-edited-a-line-last-or-what-version-it-was-last-modified-in"
-
+
+id="how-do-i-find-out-who-edited-a-line-last-or-what-version-it-was-last-modified-in" 
-<p>To have a file printed out with every line annotated with who last edited it
-and in what version on the main trunk, run:</p>
@@ -386 +386 @@
-</div>
-</div>
- id="patches"
-
- id="how-to-make-a-patch"
-
+
+id="patches" 
+
+id="how-to-make-a-patch" 
-<p>If you are using CVS (anonymous or developer) you can use CVS to make the
-patches for you. Just edit your local copy and enter the following command:</p>
@@ -398 +398 @@
-Windows version is available as part of the cygwin tools).</p>
-</div>
- id="how-do-i-apply-a-patch"
-
+
+id="how-do-i-apply-a-patch" 
-<p>For the general case, to apply a patch go to the directory that the patch was
-created from (usually /dist/src/) and run:</p>
@@ -409 +409 @@
-leaves the paths alone.</p>
-</div>
- id="how-do-i-undo-an-applied-patch"
-
+
+id="how-do-i-undo-an-applied-patch" 
-<p>Undoing a patch differs from applying one by only a command-line option:</p>
-<pre class="literal-block">
@@ -419 +419 @@
-use.</p>
-</div>
- id="how-to-submit-a-patch"
-
- 
+
+id="how-to-submit-a-patch" 
+
-<a class="reference" href="http://www.python.org/patches/">http://www.python.org/patches/</a> .</p>
-</div>
- id="how-to-test-a-patch"
-
+
+id="how-to-test-a-patch" 
-<p>Start by testing on your own system.  Python comes with an extensive
-regression test suite by running the <tt class="docutils literal"><span class="pre">Lib/test/regrtest.py</span></tt> script.
- 
- 
+
+
-<a class="reference" href="http://www.python.org/doc/lib/module-test.html">http://www.python.org/doc/lib/module-test.html</a>.</p>
-<p>If you suspect the patch may impact other operating systems, test as
@@ -437 +437 @@
-volunteered to support a particular operating system.</p>
-</div>
- id="how-to-change-the-status-of-a-patch"
-
+
+id="how-to-change-the-status-of-a-patch" 
-<p>To change the status of a patch or assign it to somebody else you have to be
-a) a SourceForge-recognized Python developer and b) a patch administrator.
@@ -456 +456 @@
-</div>
-</div>
- id="development-on-windows"
-
- id="how-to-install-cvs-and-ssh"
-
+
+id="development-on-windows" 
+
+id="how-to-install-cvs-and-ssh" 
-<p><a class="reference" href="winssh.txt">Here's a link</a> to text instructions for
-setting up a command-line CVS using SSH under Windows,
@@ -468 +468 @@
-</div>
-</div>
- id="bugs"
-
- id="where-can-i-submit-view-bugs-for-python"
-
+
+id="bugs" 
+
+id="where-can-i-submit-view-bugs-for-python" 
-<p>The Python project uses SourceForge's bug tracking facility. Go to
-<a class="reference" href="http://sourceforge.net/bugs/?group_id=5470">http://sourceforge.net/bugs/?group_id=5470</a> for all bug management
@@ -478 +478 @@
-disabled since it was too difficult to get in contact with submitters.</p>
-</div>
- id="how-do-i-use-the-sourceforge-bug-manager"
-
+
+id="how-do-i-use-the-sourceforge-bug-manager" 
-<p>By default, you will see the list of all Open bugs. You can change
-which bugs you're viewing by selecting the assigned_to/status/area/type
@@ -486 +486 @@
-</div>
-</div>
- id="appendix-a"
-
- id="patch-manager-guidelines"
-
+
+id="appendix-a" 
+
+id="patch-manager-guidelines" 
-<p>Intended use of SourceForge patch Resolution, Status &amp; &quot;Assigned To&quot; fields
- 
+
-16-Mar-2001</p>
-<p>In general, the Resolution and Status fields should be close to
@@ -510 +510 @@
-meant to force your attention periodically: patches get harder &amp; harder to
-deal with the longer they sit.</p>
- id="status-open-resolution-none"
-
+
+id="status-open-resolution-none" 
-<p>The initial state of all patches.
-The patch is under consideration, but has not been reviewed yet, or
@@ -536 +536 @@
-Open and bring it up on Python-Dev.</p>
-</div>
- id="status-open-resolution-accepted"
-
+
+id="status-open-resolution-accepted" 
-<p>The powers that be accepted the patch, but it hasn't been applied yet. [xxx
-flesh out -- Guido Bottleneck avoidable here?]</p>
@@ -545 +545 @@
-apply it (the submitter if possible).</p>
-</div>
- id="status-closed-resolution-accepted"
-
+
+id="status-closed-resolution-accepted" 
-<p>The patch has been accepted and applied.</p>
-<p>The previous Resolution was Accepted, or possibly None if the submitter was
-Guido (or moral equivalent in some particular area of expertise).</p>
-</div>
- id="status-closed-resolution-rejected"
-
+
+id="status-closed-resolution-rejected" 
-<p>The patch has been reviewed and rejected.</p>
-<p>There are generally no transitions out of this state:  the patch is dead.</p>
-<p>The person setting this state should also assign the patch to None.</p>
-</div>
- id="status-open-resolution-out-of-date"
-
+
+id="status-open-resolution-out-of-date" 
-<p>revious Resolution was Accepted or Postponed, but the patch no longer
-works.</p>
@@ -565 +565 @@
-<p>Also assign it back to the submitter, as they need to upload a new version.</p>
-</div>
- id="status-open-resolution-postponed"
-
+
+id="status-open-resolution-postponed" 
-<p>The previous Resolution was None or Accepted, but for some reason (e.g., pending
-release) the patch should not be reviewed or applied until further
@@ -576 +576 @@
-able and willing to decide when the state should change again.</p>
-</div>
- id="status-deleted"
-
+
+id="status-deleted" 
-<p>Bit bucket.</p>
-<p>Use only if it's OK for the patch and its SourceForge history to