[Python-Dev] Possible issue with 2.5a1 Win32 binary (original) (raw)
Paul Moore p.f.moore at gmail.com
Thu Apr 6 10🔞59 CEST 2006
- Previous message: [Python-Dev] Possible issue with 2.5a1 Win32 binary
- Next message: [Python-Dev] Possible issue with 2.5a1 Win32 binary
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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 badcoding 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.
- Previous message: [Python-Dev] Possible issue with 2.5a1 Win32 binary
- Next message: [Python-Dev] Possible issue with 2.5a1 Win32 binary
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]