so that this doesn't get lost...

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.

It's not a difference between versions, but a difference between
old-style and new-style classes (which derive from object).
In 3.0, all classes are new-style...

Humberto, I added your test file in trunk.
I added some other tests: now pydocfodder.py is used by a basic "smoke
test".
The tests revealed two bugs in python3.0...  Thanks!

Amaury, seems that there's duplicated from render_doc inside pydoc.doc. I 
removed it and everything kept working, including the new basic tests.

According to Georg, the "adaptation" referred by this issue is just about 
changing the URLs in the documentation to point appropriately to the URLs 
generated by the new doc system.

Anyway, the doc-cleanup.patch is still pending... ;)

> Anyway, the doc-cleanup.patch is still pending... ;)
No, I already removed the duplicated code in r62505.

OK, this is fixed by including topic help as a separate module, and not
relying on the HTML documentation, in r63871.