git dependencies are not cached

[blaggacao]

• I am on the latest Poetry version.
• I have searched the issues of this repo and believe that this is not a duplicate.

• Poetry version: Poetry 0.12.17
• Link of a Gist with the contents of your pyproject.toml file: https://gist.github.com/blaggacao/34765d9ce6d0783297952f1802b69c45

Issue

I checked the code and it seems the temp dir for git dependency installs are not cached. This is a bug-like behaviour for a 1.5 GB repository like https://github.com/odoo/odoo

[blaggacao]

Specifically:
https://github.com/sdispater/poetry/blob/e01564775bf58b3f11a5aa67841e9b4cb79de176/poetry/installation/pip_installer.py#L231-L232

And:
https://github.com/sdispater/poetry/blob/736c6d358410cfdb718b2a4ea8af091ba8290261/poetry/puzzle/provider.py#L212

[blaggacao]

Maybe this issue can serve as an opportunity to streamline poetry.vcs.git with pygit2 libgit bindings...

[ubmarco]

I also observed that a Git dependency given as

[tool.poetry.dependencies]
python = "^3.6"
click = "^7"
PyYAML = "*"
pdfplumber = { git = "https://github.com/jsvine/pdfplumber.git", rev = "df00787" }

will be cloned every time I do a poetry install, even if .venv/src/pdfplumber already contains the Git checkout with the right commit ID. I see no reason why an update is needed.
This prevents running tests when machines are offline.

[ldhieu]

Having issues with this as well.

Does anyone have a temporary/quick fix for this ? Running poetry add with odoo in the pyproject file takes 20-30 mins everytime

[kshcherban]

Having issues with this as well.

Does anyone have a temporary/quick fix for this ? Running poetry add with odoo in the pyproject file takes 20-30 mins everytime

Just use odoo as a submodule in your git repo and change dependency from git to path.

[dimbleby]

#6131 should have avoided cloning when nothing has changed

[abn]

This issue does not exist in Poetry 1.8.4 as the clone is reused if nothing has changed.

If the the issue still exists, or can be reproduced please create a new issue linking to this one as the codebase has changed significantly since this issue was raised.