-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Poetry 1.1.2 does not export dependency url for nested git dependencies #3115
Comments
@abn Could you please have a look? |
I have a similar problem in version 1.1.2. In
In
Result of
and it wrong, I expect:
Sorry for my English |
Can you please try the fix at #3119. Using pipxpipx install --suffix=@3119 'poetry @ git+https://github.com/python-poetry/poetry.git@refs/pull/3119/head' Using a container (podman | docker)podman run --rm -i --entrypoint bash python:3.8 <<EOF
set -e
python -m pip install -q git+https://github.com/python-poetry/poetry.git@refs/pull/3119/head
python -m poetry new foobar
pushd foobar
sed -i /pytest/d pyproject.toml
python -m poetry add 'git+ssh://git@github.com/moneymeets/sampleproject.git#83068b995c2f94b0d51333b932b1a939084e9ef7'
python -m poetry export -f requirements.txt --without-hashes
EOF Note: The container example will require authorised pubkeys or the dependency references to be updated to anonymous ssh urls or https urls. |
I'm having a similar issue with nested relative path local dependencies on poetry 1.1.2:
It appears that poetry@3119 fixes it:
Not a problem, but interestingly, many lines now include the python_version restrictions (all of my internal dependencies and many third party libraries). |
Closing this, since the problem is finally resolved in #3119. |
Resolves: python-poetry#3115 (cherry picked from commit 04967db)
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
-vvv
option).Issue
Regarding to the PR #3089 the dependencies are not exported correctly.
The exception does not occur anymore, but the git url of the nested git dependency is missing in the requirements.txt.
The output of the export command in the sampleproject repository is as expected.
You can reproduce this issue with the linked pyproject.toml.
The text was updated successfully, but these errors were encountered: