The conversation

Lessons learnedExperience excerpt · English

Having encountered poetry recently for the first time, it was "simply" hell

Having encountered poetry recently for the first time, it was "simply" hell. I just wanted to use a single file python project, https://github.com/rumpelsepp/oscclip I spent about three hours trying to figure out how to setup python keyrings to work, to let me just get started using poetry. On a system I was ssh'ed I to. Gnome-keyring-daemom was up. I spent a while adding random pam rules suggested by archwiki in to inject more gnome-daemon stuff in my envs. Random gnome-keyring-unlock scripts, which quickly start talking about Clevis and tpm and fido 2-factor. Wading through hundreds of responses about Seahorse, a gui tool unsuitable for ssh. Many long miserable sad stories. In the end I stumbled upon someone who suggested just nulling out & turning off keyring with some config to make it have a null provider. After this the poetry project just worked. The tiny handful of deps this project has were already installed on my system, but poetry was also a task runner, instrumental for the usage of this single-file script. …

Original discussionWhy not tell people to “simply” use pyenv, poetry or anaconda226 source comments · at import
3

Community replies 0

No community replies yet. Add your perspective.

Replies from the source 3

Direct replies available in this import. Original-language excerpts.

WH

Yikes. One of my favorite features from pip is how easily you can install from a git repo, or even the absolute url to the master.zip

Full original
MI

Yeah, that's the problem with all these "helpful" posts. You don't need poetry for that. My single CLI packages still use a setup.py that I haven't touched in five years and was simple enough to write.

Full original
AN

FWIW, for the case of installing Python packages as runnable tools (as opposed to importable libraries), pipx is solid. For example, you can install oscclip to a temp dir with a dedicated venv and run it immediately: $ pipx run --spec 'oscclip @ git+https://github.com/rumpelsepp/oscclip' osc-copy --help Or install it more permanently: $ pipx install 'oscclip @ git+https://github.com/rumpelsepp/oscclip' My own Zsh frontend for managing Python venvs and deps, zpy, makes use of pip-tools to accomplish the same, with its pipx clone, pipz: $ pipz runpkg 'oscclip @ git+https://github.com/rumpelsepp/oscclip' osc-copy --help $ pipz install 'oscclip @ git+https://github.com/rumpelsepp/oscclip'

Full original
Continue on Hacker News

Respect different perspectives. Share concrete experiences.

Sign in to post, reply, repost, and quote.