-
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 lock/export wrong with sys_platform (works fine on ver 1.0.10) #3112
Comments
This change ensures that markers are propagated from top level dependencies to the deepest level by walking top to bottom instead of iterating over all available packages. In addition, we also compress any dependencies with the same name and constraint to provide a more concise representation. Resolves: python-poetry#3112
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 --python '~3.8' [email protected] azureml-dataset-runtime@^1.15.0
python -m poetry lock
python -m poetry export --without-hashes | grep pywin32
EOF This hould output the following.
|
This change ensures that markers are propagated from top level dependencies to the deepest level by walking top to bottom instead of iterating over all available packages. In addition, we also compress any dependencies with the same name and constraint to provide a more concise representation. Resolves: python-poetry#3112
@abn Hi, I can confirm that the fix works! |
This change ensures that markers are propagated from top level dependencies to the deepest level by walking top to bottom instead of iterating over all available packages. In addition, we also compress any dependencies with the same name and constraint to provide a more concise representation. Resolves: python-poetry#3112 #3160
This change ensures that markers are propagated from top level dependencies to the deepest level by walking top to bottom instead of iterating over all available packages. In addition, we also compress any dependencies with the same name and constraint to provide a more concise representation. Resolves: python-poetry#3112 #3160
This change ensures that markers are propagated from top level dependencies to the deepest level by walking top to bottom instead of iterating over all available packages. In addition, we also compress any dependencies with the same name and constraint to provide a more concise representation. Resolves: python-poetry#3112 #3160
This change ensures that markers are propagated from top level dependencies to the deepest level by walking top to bottom instead of iterating over all available packages. In addition, we also compress any dependencies with the same name and constraint to provide a more concise representation. Resolves: #3112 #3160
This change ensures that markers are propagated from top level dependencies to the deepest level by walking top to bottom instead of iterating over all available packages. In addition, we also compress any dependencies with the same name and constraint to provide a more concise representation. Resolves: python-poetry#3112 #3160 (cherry picked from commit e78a67b)
I am still able to reproduce this issue with Poetry 1.1.4. I used the following
And this is the export result:
If I revert to Poetry 1.1.3, it works fine. |
The same on version 1.1.7 in docker (but not reproduced on bare linux host) |
Any news on this issue? |
Looks like this is resolved in 1.1.12 by #4686 |
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
run
poetry lock
thenpoetry export --without-hashes
version 1.0.10
version 1.1.0 & above
The text was updated successfully, but these errors were encountered: