RetroSearch Browse

Thu Apr 6 13:12:08 CEST 2006 · https://mail.python.org/pipermail/python-dev/2006-April/063484.html

Paul Moore wrote:
> On 4/6/06, "Martin v. Löwis" <martin at v.loewis.de> wrote:
>> What happens when you run
>>
>> D:\Apps\Python25\python.exe -Wi D:\Apps\Python25\Lib\compileall.py -f -x
>> badsyntax D:\Apps\Python25\Lib
>>
>> and look at the status of the program? I think also excluding bad_coding
>> might already help.
> 
> Status was 1. With -x "bad.*" it's zero, so it looks like that's the issue.

FWIW, this breaks for me too and the output of:

C:\Python25\python.exe -Wi -m compileall -f C:\Python25\Lib

includes the expected SyntaxErrors from the bad_coding and badsyntax test modules.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
---------------------------------------------------------------
             http://www.boredomandlaziness.org

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2006-April/063484.html below:

[Python-Dev] Possible issue with 2.5a1 Win32 binary