➜

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 pitrou
Recipients Dmitry.Jemerov, JingCheng.LIU, docs@python, eric.araujo, ezio.melotti, georg.brandl, orsenthil, pitrou, r.david.murray, stutzbach, terry.reedy
Date 2010-09-03.22:51:24
SpamBayes Score 0.0037339325
Marked as misclassified No
Message-id <1283554281.3223.4.camel@localhost.localdomain>
In-reply-to <1283553924.23.0.945278993936.issue9730@psf.upfronthosting.co.za>
Content 
> Generally: +1 on making sure examples in the docs are up to date.  If
> someone wants to do the tedious work of making sure that a "make
> doctest" succeeds, I'm all for it, it may involve adding a few (in
> HTML output invisible) testsetup blocks.

I'm not sure that's a good idea. It may add a lot of spurious imports
which only make the examples longer and less readable.
History
Date User Action Args
2010-09-03 22:51:25pitrousetrecipients: + pitrou, georg.brandl, terry.reedy, orsenthil, stutzbach, ezio.melotti, eric.araujo, r.david.murray, Dmitry.Jemerov, docs@python, JingCheng.LIU
2010-09-03 22:51:24pitroulinkissue9730 messages
2010-09-03 22:51:24pitroucreate