Thanks, Gabriel.

I ended up having to rewrite the batch script to call the Cilly driver from
within the Python script. I'm still not sure why I have to do this -- I
suspect that it is because the `subprocess` module -- which allows Python
to make system calls -- employs the Windows shell to make its calls. In the
Windows shell, I am unable to use either the UNIX absolute path or the
Windows absolute path to the driver to run it. I have tried to prefix the
call to the driver with the 'perl' command to be more explicit, in case the
Windows shell was ignoring the shebang, but I seem to be running into
issues specifying where perl should look to find the files that it needs
(its PATH). The batch file seems to work best for my purposes.

It is a very singular use case though, so you don't have to add it to the
CIL source code if it makes it messier. Thanks for your help! :)

On 16 September 2013 14:24, Gabriel Kerneis <gabr...@kerneis.info> wrote:

> On Mon, Sep 16, 2013 at 01:59:40PM -0700, Jonathan Kotker wrote:
> > Chances are that I may just have to write a replacement batch script for
> my
> > own purposes.
>
> For what it's worth, I got rid of cilly.bat and .exe extensions because
> they
> seemed unnecessary on modern Windows versions. But if anyone has a good
> use case
> for it, I'm not opposed to add it back (cilly.bat is only a minimalistic
> one-liner anyway, so it wouldn't add much maintenance effort).
>
> --
> Gabriel
>
------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. 
http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
_______________________________________________
CIL-users mailing list
CIL-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cil-users

Reply via email to