Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
better support for using poetry-managed scripts in crontabs
See original GitHub issueAs 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…
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
My workaround is to directly use the entrypoints installed in the poetry-managed virtualenv, but this is definitely not stale.
Hello,
similar discussion is going on in https://github.com/python-poetry/poetry/issues/2179. So I will close this one here.
fin swimmer