Nacki
curious about how do people handle
The difference here as I see is that the python script on wmill cloud has it's own self-contained dependencies to itself "as a script". Meaning, if you have two scripts in a folder in wmill, both of them can use different versions of the same package without impacting the other dependencies.
This is not the case with venvs, at least not in the way that I understand they work, if I create a venv for a local folder, all python scripts in the local folder share the same dependencies and versions. Unless there is a way to create one venv per one script in the same folder and somehow configer them to use distinct dependency files like requirements.txt // pyproject.toml, but using poetry I don't see how to do that, is that what you mean PDM supports?
6 replies