I don't know if this feature request is out of scope and/or impossible, or if it's already possible in some way.
Is your feature request related to a problem? Please describe.
It would be great to be able to use PDM as well not only locally when working in a specific PDM-set project directory, but also on a staging or production server, getting rid of virtual environments completely. For this, it would be great if we could execute a Python project with the pdm run command not only from the project directory but from anywhere (from a cron, or from a systemd file fro example), and still take into account the project dependencies context.
Describe the solution you'd like
We could, for example, pass a path to the project pyproject.toml and dependencies as an argument to the pdm run command, like pdm run /var/www/myproject/manage.py --path /var/www/myproject/pyproject.toml and/or have a descriptor of the path of the __pypackages__ in .pdm.lock.
Does that make sense?
I don't know if this feature request is out of scope and/or impossible, or if it's already possible in some way.
Is your feature request related to a problem? Please describe.
It would be great to be able to use PDM as well not only locally when working in a specific PDM-set project directory, but also on a staging or production server, getting rid of virtual environments completely. For this, it would be great if we could execute a Python project with the
pdm run
command not only from the project directory but from anywhere (from a cron, or from a systemd file fro example), and still take into account the project dependencies context.Describe the solution you'd like
We could, for example, pass a path to the project
pyproject.toml
and dependencies as an argument to thepdm run
command, likepdm run /var/www/myproject/manage.py --path /var/www/myproject/pyproject.toml
and/or have a descriptor of the path of the__pypackages__
in.pdm.lock
. Does that make sense?