test_pydoc fails on Ubuntu Lucid:

======================================================================
FAIL: test_apropos_with_bad_package (test.test_pydoc.PydocImportTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/stefan/pydev/cpython/Lib/test/test_pydoc.py", line 409, in test_apropos_with_bad_package
    self.assertEqual(b'', result)
AssertionError: b'' != b'Crypto.Protocol.AllOrNothing - This file implements all-or-nothing package transformations.\nCrypto.SelfTest.Protocol.test_AllOrNothing'

======================================================================
FAIL: test_apropos_with_unreadable_dir (test.test_pydoc.PydocImportTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/stefan/pydev/cpython/Lib/test/test_pydoc.py", line 419, in test_apropos_with_unreadable_dir
    self.assertEqual(b'', result)
AssertionError: b'' != b'Crypto.Protocol.AllOrNothing - This file implements all-or-nothing package transformations.\nCrypto.SelfTest.Protocol.test_AllOrNothing'

----------------------------------------------------------------------

I have the same one on Debian testing:

======================================================================
FAIL: test_apropos_with_bad_package (test.test_pydoc.PydocImportTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "test/test_pydoc.py", line 403, in test_apropos_with_bad_package
    self.assertEqual(b'', result)
AssertionError: b'' != b'docutils.parsers.null - A do-nothing parser.\ndocutils.writers.null - A do-nothing Writer.'

======================================================================
FAIL: test_apropos_with_unreadable_dir (test.test_pydoc.PydocImportTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "test/test_pydoc.py", line 413, in test_apropos_with_unreadable_dir
    self.assertEqual(b'', result)
AssertionError: b'' != b'docutils.parsers.null - A do-nothing parser.\ndocutils.writers.null - A do-nothing Writer.'


docutils is the first package that’s found in my user site-packages; can you tell if your Crypto package is in that same location?

Eric Araujo <report@bugs.python.org> wrote:
> docutils is the first package that???s found in my user site-packages;
> can you tell if your Crypto package is in that same location?

The package is here:

/usr/local/lib/python3.3/site-packages/Crypto/SelfTest/Protocol/test_AllOrNothing.py

The tests are (naturally) run in the cpython repo, but
/usr/local/lib/python3.3/site-packages is in sys.path.

Adding Ned, who refactored these tests, to nosy.

New changeset e5f2c04055a2 by Ned Deily in branch '2.7':
Issue #13861: Prevent test_apropos* test case failures in test_pydoc.
http://hg.python.org/cpython/rev/e5f2c04055a2

New changeset 5eb47e1732a0 by Ned Deily in branch '3.2':
Issue #13861: Prevent test_apropos* test case failures in test_pydoc.
http://hg.python.org/cpython/rev/5eb47e1732a0

New changeset ff230e366610 by Ned Deily in branch 'default':
Issue #13861: merge
http://hg.python.org/cpython/rev/ff230e366610

For the as-yet unreleased changes for Issue7425, I added some test cases for pydoc -k (apropos) and chose a keyword of "nothing", a keyword which has no hits in the standard library.  Unfortunately, you both installed third-party packages that *do* have hits for "nothing".  Cute!  I've now changed the keyword to a nonsense one which I hope will have a zero probability of getting a hit.