-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
better support for using poetry-managed scripts in crontabs #462
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
My workaround is to directly use the entrypoints installed in the poetry-managed virtualenv, but this is definitely not stale. |
Anyone got any ideas on this? I'd hate to have to use pipenv for cron scheduled scripts. |
The stale bot already marked this as stale once. It's been about 7 months since the last post. This issue keeps coming up for me, and there hasn't been any activity on it. |
Hello, similar discussion is going on in #2179. So I will close this one here. fin swimmer |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
As requested on Discord...
@sdispater 's current answer was: Well, since Poetry needs to be run inside the directory of the project, you would have to create a shell script that cd into the project's directory then execute poetry install and finally poetry run my-script.
I hope that install step would only need to be done once? I'm wondering if using
cd /abs/to/folder-containing-pyprojects.toml/ && /abs/to/poetry run my_command and --its options
would currently work?Anyway, this feature request is to support this with something nice, the idea I suggested was:
/abs/to/poetry -p /abs/to/folder-containing-pyprojects.toml/ run my_command and --its options
Maybe
-p
could even be--cd
. I'm happy to work on a PR for this as soon as it's confirmed that it would likely be merged...The text was updated successfully, but these errors were encountered: