You could use atexit to write a small file (flag. Txt) when script1. Py exits.Mainscript.
Py could regularly be checking for the existence of flag. Txt and when it finds it, will kill program. Exe and exit.
You could use atexit to write a small file (flag. Txt) when script1. Py exits.Mainscript.
Py could regularly be checking for the existence of flag. Txt and when it finds it, will kill program. Exe and exit.
Edit: I've set persistent environment variables using this, but I only use it for python-based installation scripts. Usually I'm pretty shy about messing with the registry.(this is for windows btw).
I found a way to set an environment variable, but it looks like it is not persistent...once Script1. Py finishes, the variable is deleted. So I may end up doing this if all else fails... – hahuang65 May 29 '09 at 0:02 If you want setting the environment variable to be persistent, you have to actually get into the registry.
But I really don't recommend this approach for setting flags in a kind of IPC. – Ryan Ginstrom May 29 '09 at 7:12.
This seems like a perfect use case for sockets, in particular asyncore.
Thanks, not at work anymore, but I will try this tomorrow :) – hahuang65 May 29 '09 at 7:11.
You cannot use environment variables in this way. As you have discovered it is not persistent after the setting application completes.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.