This has to be done whenever there is a clear install process, which is not the case yet. Would that be an install script ? If so, compare install processes of early version of nvm for instance . Would that be a pip-installable command-line package instead ?
Should venvs be slightly refactored to make it a smoother command-line tool with argument parsing (using shell techniques or python libraries such as argparse) and get something along the lines of venvs setup, venvs generate, venvs upgrade ? Or should we keep the status quo with the current sourced functions ?
Besides, within the README, it has to be made clear which shells are supported (this is bash and zsh) and maybe explain why kshis not supported. However, it has to be decided first if some environment variable VENVS_SOURCE_DIR could be set from the outside so that other shells such as dash could be supported as well (as there is no POSIX way to check the sourced script name)
This has to be done whenever there is a clear install process, which is not the case yet. Would that be an install script ? If so, compare install processes of early version of nvm for instance . Would that be a pip-installable command-line package instead ?
Should
venvsbe slightly refactored to make it a smoother command-line tool with argument parsing (using shell techniques or python libraries such as argparse) and get something along the lines ofvenvs setup,venvs generate,venvs upgrade? Or should we keep the status quo with the current sourced functions ?Besides, within the README, it has to be made clear which shells are supported (this is
bashandzsh) and maybe explain whykshis not supported. However, it has to be decided first if some environment variableVENVS_SOURCE_DIRcould be set from the outside so that other shells such asdashcould be supported as well (as there is no POSIX way to check the sourced script name)