- OS version: Ubuntu 20.04.6 LTS
- Poetry (version 2.1.2)
- Python version: 3.10
Issue:
Sort of a follow up to #145
my pyproject.toml file specifies a local dependency:
[tool.poetry.dependencies]
my_pkg = {path = "../../../my_pkg", develop=true}
The poetry.lock file specifies my_package with a relative path, which is correct.
But running poetry export --output requirments.txt results in
# requirements.txt
-e file:///full/path/to/my/local/dependency/my_pkg;
this requirement.txt becomes unusable in CI due to the absolute path. There should be an optional to make the path in requirements.txt local path instead.
I am on the latest Poetry version.
I have searched the issues of this repo and believe that this is not a duplicate.
Issue:
Sort of a follow up to #145
my
pyproject.tomlfile specifies a local dependency:The
poetry.lockfile specifies my_package with a relative path, which is correct.But running
poetry export --output requirments.txtresults inthis
requirement.txtbecomes unusable in CI due to the absolute path. There should be an optional to make the path inrequirements.txtlocal path instead.