[issue13861] test_pydoc failure
Éric Araujo
report at bugs.python.org
Fri Feb 3 14:47:12 CET 2012
Éric Araujo <merwok at netwok.org> added the comment:
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?
----------
nosy: +eric.araujo
versions: +Python 3.2
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue13861>
_______________________________________
More information about the Python-bugs-list
mailing list