<br><br><div class="gmail_quote">On Fri, Aug 26, 2011 at 7:56 AM, Paul Grenyer <span dir="ltr"><<a href="mailto:paul.grenyer@gmail.com">paul.grenyer@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi Peter<br>
<div class="im"><br>
> if you are running windows:<br>
><br>
> if you end up in the wrong directory after failure you could use<br>
> sub-batch-files (call xxxx.bat ....) and in that sub-batch-files you could<br>
> use the command setlocal. Then environment and working directory are<br>
> restored on return from the batch file.<br>
<br>
</div>Yeah, that feels like quite a hack. It's odd you can't set the working<br>
directory for the python executable.<br>
<br>
Any ideas about my command line argument problem?<br>
<div class="im"><br></div></blockquote><div><br></div><div><br></div><div>Can you show the console output that makes you think it's pulling the second argument as a python file to execute?</div><div><br></div><div>Thanks,</div>
<div><br></div><div>slide </div></div>