consider multiple different chaintool versions on same system
Opened this issue · 1 comments
This could happen e.g. if you installed version 1.2 in the site-packages for Python 3.7, and then later installed version 1.3 in the site-packages for Python 3.8. If these versions don't use compatible formats, and both of them later get run, what happens?
Perhaps we should use version-isolation in the appdirs. The init functions could copy things over from old version-specific subdirectories to new (and do any necessary translations). The current overwrite behavior for the generated completion scripts would not be necessary. That doesn't solve everything though, notably the PATH for shortcuts (which shortcuts should be on the path?) and the user dir for lazy completion load. Hmm.
I guess for now, completions.init should only overwrite if current version is NEWER than old version, not just if it's different. That might be sufficient if (once I hit version 1.0) I can avoid backwards-incompatible changes in data and configurations. Might be tough though!
Mostly handled by ad5bb1b ... need to ponder what (if anything) the completions helper script should worry about here.