Superrrr minor ask here and one that I’ve already solved for myself technically. I have started migrating over to using the TDPyEnvManagerHelper, and I’m setting up a install script so that I can install my ENV on my different computers. I’m using a requirements.txt to manage my libraries and it would be nice to have –useReqs as a command line arg, in addition to the other common functions. I know it’s all accessible by just calling the python script, but if there’s gonna be a command line parser situation it would nice to be able to have more options. Again It’s a great tool and I’ve already implemented the change on my own file so if this doesn’t happen I get it.
New CLI arguments:
--useReqs
Python vEnv mode: install requirements after creating/using the venv.
Runs even if the venv already exists (explicit install pass is run)
--requirementsFiles <file1> <file2> ...
Python vEnv mode: optional explicit requirements files used with --useReqs.
If omitted, defaults to requirements.txt in current working directory.
--useEnvYml
Conda mode: create environment from environment.yml if present.
Small question, is there a reason to prefer camelCase for naming? This is not something Python ecosystem generally use and it seems TD is adopting it even more with each new feature.
We prefer to use camelCase in TD for this. That’s our internal standard. They are different parts of the software where snake_case is used or PascalCase is used.