Nice post!
Here are some commands that I use on a (nearly) daily basis:
I like to have my venvs in the same folder than my project, and so I use this config to update the default behavior of Poetry:
poetry config virtualenvs.in-project true
For installing projects that uses poetry but that are not packages themselves, I use this command:
poetry install --no-root
For deleting some annoying cache (in case poetry don't detect a new version of a package), I use:
poetry cache clear pypi
For installing a package from github/gitlab (bonus if it's on a branch), I use:
poetry add git+https://github.com/user/package.git@branch_name
For installing a particular version of a package (like django-treebeard, when the latest version broke django-cms), I use:
poetry add "django-treebeard>4.0,!=4.5.1"
I was looking for that in-project env config ๐ thanks for these tips
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Nice post!
Here are some commands that I use on a (nearly) daily basis:
I like to have my venvs in the same folder than my project, and so I use this config to update the default behavior of Poetry:
For installing projects that uses poetry but that are not packages themselves, I use this command:
For deleting some annoying cache (in case poetry don't detect a new version of a package), I use:
For installing a package from github/gitlab (bonus if it's on a branch), I use:
For installing a particular version of a package (like django-treebeard, when the latest version broke django-cms), I use:
I was looking for that in-project env config ๐ thanks for these tips