Ideas

[rcaneill]

So here is the story:

I had a pipenv environment that I somehow broke when installing a package. I did not had proper git versionning of the Pipfile and Pipfile.lock so I spent 3 days correcting my error. In the meantime I also shifted from pipenv to poetry. Anyway, I need to ensure that this will never happen to me again!

Now, how to do it? The idea is to create a new git branch before updating / installing a new package, do all stuff in this branch, run tests, and if everything is fine, merge to master.

Sticky notes:

• Use poetry.toml (or poetry config --local virtualenvs.path ~/tmp/pypoetry)

$ cat poetry.toml
[virtualenvs]
path = "/home/romain/tmp/pypoetry"

• Use git branch --show-current or echo $(git branch --show-current) to use git branch name in virtualenvs.path

[rcaneill]

• Think how to write tests for the updates / installs
• Think how to write tests for this repository
• What language to use? Python? Bash?

[rcaneill]

See https://python-poetry.org/docs/configuration/#settingsvirtualenvspath-string

[rcaneill]

See python-poetry/poetry#1579

[rcaneill]

See python-poetry/poetry#2404