On 11/7/2014 12:19 PM, Anurag Sharma wrote: > I am able to proceed proceed further on changing all the instances of > 'python3.2' | 'python32.exe' with python and python32.exe
This is a little odd. The only thing I can think of here is that something in the stack (Java, ant, or maybe even Windows itself) is trying to treat ".2" as the filename extension in a throwback to the 8.3 days of DOS -- and failing because not only does "python3.2" not exist as a full filename, but ".2" is not the extension for an executable. Windows may have long filenames, but under the covers, it still thinks in the old 8.3 filename structure. in a command prompt, go to your home directory (C:\Users\username for most recent versions) and type "dir /x" to see both the long and short filenames. One fix would be to use "python3" as the executable name and somehow detect that it's at least version 3.2. If the output from "python3 --version" cannot be parsed easily by ant, perhaps a simple python script can be written and included that throws a nonzero exit code if an incompatible version is used, which hopefully can abort the build. I think that might be the easy fix. Whether it's the right fix is something I have to ask those who are a lot better at wrangling ant. Thanks, Shawn --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
