David Hotham

IMO `--dry-run` is sufficient.

Poetry uses [virtualenv](https://github.com/pypa/virtualenv), you will want to take this to that project

duplicate #9635, #9291 no reason to think there is a poetry bug here - but the reporters do not seem to have explained what, if anything, they understood. If and...

Too bad, probably. I don't know any way to tell ssh always to fail non-interactively here. If it shows up in verbose mode, that'll probably have to be good enough...

poetry uses dulwich for git clones, so next step is to persuade dulwich to use that parameter then suggest you experiment with something like ```diff diff --git a/src/poetry/vcs/git/backend.py b/src/poetry/vcs/git/backend.py index...

your issue was correctly closed because it is a duplicate of this one, there is no value in having both. This one is still open. there is a pull request...

this one is well understood, we are just waiting for someone to show up with a workable pull request cf https://github.com/python-poetry/poetry/issues/9618#issuecomment-2546524392

This would count as a bug I think if presented as "when I use poetry-specific dependency notation in pyproject.toml, then `poetry build` produces a wheel containing invalid metadata". But then...

You are not publishing a wheel, you are publishing only a source distribution - see https://pypi.org/project/grad-cam/#files. The way installation of python packages works is always from wheel: so currently every...

Poetry is doing an editable install. "The same way as pip" is not a goal, but `pip install -e path` is a closer equivalence. Though nb there is more than...