This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients brett.cannon, chris.jerdonek, docs@python, eric.araujo, ezio.melotti, georg.brandl, r.david.murray, sbt
Date 2012-08-13.00:58:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1344819519.47.0.999764124861.issue15629@psf.upfronthosting.co.za>
In-reply-to
Content
The point of running the doctests in the docs to to make sure the *docs* are correct, not to make sure Python is correct.  So IMO adding them to regrtest is much more trouble than the tiny benefit it would produce for test coverage.  On the other hand, having 'make doctest' run when '-uall' is specified would be cool, if the tests can thus be run by the buildbots.

But I think should be 'make doctest', and not regrtest using doctest to process .rst files.  The reason is that Sphinx has extra facilities that allow docttests to work without having to have "boilerplate" code in places where doing so would disrupt the narrative flow.  I could be mis-remembering (and Georg will correct me if I am misremembering again :), but I don't think those work when doctest is used directly against the .rst file.
History
Date User Action Args
2012-08-13 00:58:39r.david.murraysetrecipients: + r.david.murray, brett.cannon, georg.brandl, ezio.melotti, eric.araujo, chris.jerdonek, docs@python, sbt
2012-08-13 00:58:39r.david.murraysetmessageid: <1344819519.47.0.999764124861.issue15629@psf.upfronthosting.co.za>
2012-08-13 00:58:38r.david.murraylinkissue15629 messages
2012-08-13 00:58:38r.david.murraycreate