Ok, since seem to have issues with compiling executables into workable/running modules using certain distribution tools, if I try to implement certain bits of functionality, but, if I sort of split the pieces up into separate apps, and compile them separately, using different sets of tools, etc., then it's just possible they'll handle their specific bits of functionality, however, will still want to be able to pass sort of arguments/values back and forth during operation/while executing, so am considering something like passing the path to something like a pair of text files to the second app as a command line argument, and then during it's operations, it can check one of them as a sort of status update argument delivery method, and then when it's completed it's operations, it could first generate the second file to thus pass output values back to first app, which could, on it's own sort of monitor for the appearance of that second text file?
Alternatively, what would maybe be a better method for passing string/numeric values back and forth between two separate executables in this style/sense? Something like peek/poke back in ooooold days, or something like writing values to windows registry? Don't think that it should really be necessary, and think something as simple as either just passing values back and forth in temporary text files, or sqlite database files, or even just pickled python objects could do the trick, but, what do you guys think? TIA Jacob Kruger Blind Biker Skype: BlindZA "Roger Wilco wants to welcome you...to the space janitor's closet..."
_______________________________________________ python-win32 mailing list python-win32@python.org https://mail.python.org/mailman/listinfo/python-win32
