On Nov 30, 4:03 pm, Andrew Berg <bahamutzero8...@gmail.com> wrote: > I've done some research, but I'm not sure what's most appropriate for my > situation. What I want to do is have a long running process that spawns > processes (that aren't necessarily written in Python) and communicates > with them. The children can be spawned at any time and communicate at > any time. Being able to communicate with non-local processes would be > nice, but is not necessary. The implementation needs to be > cross-platform, but child processes will use the same OS as the parent > during runtime. > I don't think I'll ever need to transfer anything complicated or large - > just strings or possibly tuples/lists. I'd rather not go outside the > standard library (but I'd consider it). I don't need to worry about > compatibility with older Python versions; if it only works with Python > 3.2, that's not a problem. > I'm thinking sockets, but perhaps there's something simpler/easier. > > -- > CPython 3.2.2 | Windows NT 6.1.7601.17640 | Thunderbird 7.0
You might want to take a look at the SIMPL toolkit. http://www.icanprogram.com/06py/lesson1/lesson1.html SIMPL modules can be written (and mixed) in any number of supported languages including Python, C, C++, JAVA, Tcl/Tk or PHP. Non local communication is handled by generic surrogates. Because of this surrogate architecture SIMPL modules can often be tested locally and then deployed into the cloud without any changes. bob -- http://mail.python.org/mailman/listinfo/python-list
