Can I kill a previous called script (PY.ExecFile)

[marcusvdt]

I'm developing some complex code using Python. This python script is called with PY.ExecFile on VC startup so I can use the functions further with PY.ExecString.
This is a wonderful feature IMO which adds unlimited power to the already powerful VC.

Sometimes I would like to kill the script so I can test a modification or a correction that I just made. Since it stays in memory, the only way I know to do this is to perform a full restart of VC.

I tried using the reinitialize python command from the Python editor, but it seems the threads which have been started by the script still remain running.
Is this correct or I'm doing something wrong?
Is there a quicker way to force killing or restarting a specific python scripts?

Sorry if I'm being stupid somehow... Thank you.

[jitterjames]

You are doing what you are supposed to. Reinitializing was created for this purpose, but spawned threads seem to survive even after the entire Iron Python object is destroyed and recreated.

I will take another look to see if there is anything I can do, but for now you'll need to either keep restarting VC or actually keep all your threads in a list or something so you can call a function to kill them all yourself.

For what it's worth, I've been restarting VC over and over again myself when in this situation.

[jitterjames]

I just banged my head against this one (again) for about 1.5 hours.  I am not able to find a direct solution.

However, I can propose a sort of workaround.

I will make a small change to the "Reinitialize Python" function so that it sets a variable named killPy to true.

Any thread that is running forever will probably look a little bit like this:

Code: [Select]

while 1:
        try:
            ...
            ...
       
        except:

change it to look like this and it should stop looping when you reset the python engine:

Code: [Select]

while not killPy:
        try:
            ...
            ...
       
        except:

I know it is not perfect but it will have to do, and in situations where it does not work then we will just have to restart VC.

[marcusvdt]

Thanks James! The workaround seems more than enough.
Is it coming on the next release already? Perhaps tomorrow?

Just kidding! 
no hurry!

You guys are fast with your support!
Thanks!

[jitterjames]

I am actually planning to release a bug-fix version soon anyway, so hopefully within a day or two. 

[jitterjames]

It's out:

http://voxcommando.com/mediawiki/index.php?title=ChangeLog#Version_2.1.5.1