Jason Vas Dias <jason.vas.d...@gmail.com> added the comment:
Oops, bash <TAB> completion was a bit over-eager, and I inadvertently
built /usr/src/Python-2.7 instead of /usr/src/Python-2.7.1 .
Nevertheless, when I finally do build Python-2.7.1, I get the same
error :
test_commands
test test_commands failed -- Traceback (most recent call last):
File "/usr/src/Python-2.7.1/Lib/test/test_commands.py", line 61, in
test_getstatus
self.assertTrue(re.match(pat, commands.getstatus("/."), re.VERBOSE))
AssertionError: None is not True
I guess if python-2.7 cannot run command I'd know about it, and
it has the same bug.
I guess you ship a broken 'test_commands' test script for Python-2.7
AND Python-2.7.1 .
This does not increase my already meager confidence in Python's
robustness and reliability.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue11946>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
