![]() My understanding was that shell=True should be spawning a sub-shell, but I guess I it is spawning one in a way that is shared between each call. ![]() Is there a better way to handle highly-interactive shells than this? I'd considered kicking off a screen for each instance, but thought there was a cleaner way. I have the code I normally use for this kind of thing, with crawl replacing other applications I've thrown a GA at. However, with dcss being quite interactive having a shared subshell seems to be problematic. In the past when I've used a pool to evaluate similar code (genetic algorithms), I've used subprocess.call to split off each process. ![]() I am trying to run multiple instances of a console-based game (dungeon crawl stone soup - for research purposes naturally) using a multiprocessing pool to evaluate each run.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |