This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Jason.Vas.Dias
Recipients Jason.Vas.Dias
Date 2011-04-28.15:07:28
SpamBayes Score 4.892215e-08
Marked as misclassified No
Message-id <1304003251.31.0.511148649851.issue11946@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2011-04-28 15:07:32Jason.Vas.Diassetrecipients: + Jason.Vas.Dias
2011-04-28 15:07:31Jason.Vas.Diassetmessageid: <1304003251.31.0.511148649851.issue11946@psf.upfronthosting.co.za>
2011-04-28 15:07:29Jason.Vas.Diaslinkissue11946 messages
2011-04-28 15:07:28Jason.Vas.Diascreate