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. I guess that means the pywin32 problem is unrelated - I'll raise that as a separate bug. Thanks for the help with this! Paul.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4