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 scoder
Recipients collinwinter, scoder
Date 2008-06-01.14:37:21
SpamBayes Score 0.06004524
Marked as misclassified No
Message-id <1212331047.91.0.677781535819.issue3020@psf.upfronthosting.co.za>
In-reply-to
Content
Running a doctest with Py2 syntax in Py3 currently involves either
running the 2to3 tool by hand or writing code to convert the doctest
using lib2to3, and then running the modified version. This basically
pushes the burden of automating this step in any test runner script in
the world onto the authors or users of these scripts.

Writing portable code is hard enough, but writing portable doctests that
remain user readable should not remain as hard as it currently is. The
doctest module in Py3 should have a simple option to run a Py2 doctest
(in a file or doc string) without requiring users to write the glue code
for it.

On a related note, if a 3to2 tool becomes available, this should be
directly supported by doctest in Py2.6.
History
Date User Action Args
2008-06-01 14:37:30scodersetspambayes_score: 0.0600452 -> 0.06004524
recipients: + scoder, collinwinter
2008-06-01 14:37:28scodersetspambayes_score: 0.0600452 -> 0.0600452
messageid: <1212331047.91.0.677781535819.issue3020@psf.upfronthosting.co.za>
2008-06-01 14:37:26scoderlinkissue3020 messages
2008-06-01 14:37:23scodercreate