When the design switched from invoke-by-subprocess to invoke-by-import, that switched the design from one where every operation instance was in a separate process to one where all operations share the same process. Yes the python namespace had to be altered so that each operation was in its own namespace (switch from the global namespace to a class namespace with each instance being separate), but now the one process has to be able to run git operations in different ElectionData clones.
(Well, maybe not depending on what the web server is doing, but I don't know that design aspect yet.)
So, add another generic option, --election_data, which can override the default "." and point to a different git clone-workspace in which to run commands. FWIIW I have been wanting to do this to make testing and debugging easier on the finger tips.
When the design switched from invoke-by-subprocess to invoke-by-import, that switched the design from one where every operation instance was in a separate process to one where all operations share the same process. Yes the python namespace had to be altered so that each operation was in its own namespace (switch from the global namespace to a class namespace with each instance being separate), but now the one process has to be able to run git operations in different ElectionData clones.
(Well, maybe not depending on what the web server is doing, but I don't know that design aspect yet.)
So, add another generic option, --election_data, which can override the default "." and point to a different git clone-workspace in which to run commands. FWIIW I have been wanting to do this to make testing and debugging easier on the finger tips.