Repository navigation
Issue #4201 Persists Despite PR #186 #5244
Description
-
I am on the latest Poetry version.
-
I have searched the issues of this repo and believe that this is not a duplicate.
-
If an exception occurs when executing a command, I executed it again in debug mode (
-vvvoption). -
OS version and name: Windows 10 Enterprise, 20H2
-
Poetry version: 1.2.0a2
-
pyproject.tomlfile:
[tool.poetry]
name = "problem"
version = "0.1.0"
description = "problem"
authors = ["problem"]
[tool.poetry.dependencies]
pywin32 = "^301"
[build-system]
requires = ["poetry-core>=1.0.0"]
build-backend = "poetry.core.masonry.api"Issue
Although #186 claims to have fixed parsing of wildcards dependency constraints (see #4095, #4201, and #4176), this issue persists.
By chance, does py install-poetry.py --preview not update to latest master branch commit?
Activity
finswimmer commentedon Feb 28, 2022
Hello @adam-grant-hendry,
until now there is now release of poetry-core that contain the workaround introduced in python-poetry/poetry-core#186 I hope we can get it out this or next week.
fin swimmer
adam-grant-hendry commentedon Feb 28, 2022
@finswimmer Oh I think I see, thank you. PR #186 is listed as merged, but it was decided to put the "fix" into release
1.1.0a7PR #289. Are you saying this PR is not yet released, but you are hoping to get it out this week or next?thejohnfreeman commentedon Mar 12, 2022
Any updates? It seems like "this or next week" has already passed.
poetry self update --previewstill installs 1.2.0a2 for me, which chokes trying to install pytest (or pytest@^6) because some dependency, which seems unspecified even with-vvv, has invalid PEP 440 version "3.9.6+".finswimmer commentedon Mar 12, 2022
poetry self updateonly updates to a new version of poetry and not in case there is a new version of poetry-core (I'm working on changing this). So please reinstall the current prerelease of poetry and the new poetry-core release will be picked up.github-actions commentedon Mar 2, 2024
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.