On 11/9/2014 8:39 AM, Shawn Heisey wrote: > The last way would utilize ant itself to check the python version as a > prerequisite, sorta similar to how it fails if it does not detect a > suitable ivy version. If we build the small script I described in my > last message and use it in an ant target called something like > "-python-minimum-version" that is called before any of the targets that > USE python, we should end up with the build failing with a helpful > message. This should be the least intrusive change. I am not a skilled > python programmer, but I could give it a try.
I came up with a script that seems to work, but when I call it in an ant target, it doesn't stop the build. This is the patch I've built so far: http://apaste.info/BQo The patch places the new target as the first dependency on nightly-smoke, but when I run "ant nightly-smoke" with python3.2 symlinked to python2.7, this is the beginning of the output. It runs this new target, but the target does not fail the build: ----------- Buildfile: /home/elyograg/asf/trunk/build.xml clean: clean: clean: -python-minimum-version: clean: clean: clean: -nightly-smoke-java8params: nightly-smoke: [python32] Python 2.7.6 ----------- I figure the reason it's not working is some kind of beginner mistake, but I haven't been able to spot it. Anyone have any ideas? Thanks, Shawn --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
