Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

My workaround for that is to initialize every checked-out copy like so:

    pyenv install -s
    pyenv exec pip install poetry
    pyenv exec poetry install
That incantation goes into my README.md.

Inconvenient, but I’ve come to accept it. I only need to run it after initial checkout and when the .python-version changes.



Interesting! I like managing poetry at the user level with pipx, so my usual incantation is

    pyenv local 3.11.0
    poetry init
    poetry env use $(pyenv which python)
    poetry install




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: