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 hdiogenes
Recipients georg.brandl, hdiogenes
Date 2008-04-24.06:47:16
SpamBayes Score 0.018126134
Marked as misclassified No
Message-id <1209019640.54.0.380626876351.issue1883@psf.upfronthosting.co.za>
In-reply-to
Content
It looks like there are no automated tests for pydoc; it's even listed in test_sundry.py.

There's only one file Lib/test/pydocfodder.py which defines "Something just to look at 
via pydoc", but isn't used anywhere (I grepped and found nothing).

I've attached a patch just to document one point where pydoc behavior differs from 2.5 to 
3.0: describe() used to return 'instance of ClassX', now it returns only 'ClassX' (which 
means this test will pass in 2.5 but not in 3.0).

Functions main and test_main were copied from test_modulefinder.
History
Date User Action Args
2008-04-24 06:47:21hdiogenessetspambayes_score: 0.0181261 -> 0.018126134
recipients: + hdiogenes, georg.brandl
2008-04-24 06:47:20hdiogenessetspambayes_score: 0.0181261 -> 0.0181261
messageid: <1209019640.54.0.380626876351.issue1883@psf.upfronthosting.co.za>
2008-04-24 06:47:19hdiogeneslinkissue1883 messages
2008-04-24 06:47:18hdiogenescreate