[issue11946] 2.7.1 'test_commands' build test fails

Jason Vas Dias report at bugs.python.org
Thu Apr 28 17:07:31 CEST 2011


Jason Vas Dias <jason.vas.dias at 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 <report at bugs.python.org>
<http://bugs.python.org/issue11946>
_______________________________________


More information about the Python-bugs-list mailing list