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 i
Thanks for the quick reply, Gabriel.
I think the main issue seems to be that for some reason, I am not able to
issue a command to run the Cilly executable from within the Python script.
In prior versions, I was able to run the cilly.bat script. It could just be
a problem with the Python script its
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 h
On Mon, Sep 16, 2013 at 01:12:34PM -0700, Jonathan Kotker wrote:
> Do you have any suggestions on why this might be the case, or how I might be
> able to get the installation to generate a batch script or an executable?
cilly.bat has indeed disappeared, but I have tested on cygwin the new pattern
Hi Gabriel.
Thank you very much for pushing this new change to CIL through. I am
currently trying to work with the new version of CIL and to re-integrate it
into my research tool, but I find myself running into a few problems.
In particular, the older version of CIL yielded a batch script (cilly.
