You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm dealing with #4523 across quite a few poetry projects. The problem appeared to be some regression between poetry-core 1.0.4 and 1.0.5. Pinning the poetry client's poetry-core==1.0.4 seems to work in the short-term, but I'm not crazy about the hack/patch.
poetry itself depends on poetry-core^1.1.0a6, which was released on July 30th, 2021, when the latest 1.0.x release was 1.0.3 on April 2021. Since then, the 1.0.x releases have seen updates up to 1.0.7, notably where 1.0.6 claims to have fixed this (via #207).
My question is: would it be possible to release 1.1.0a7 that includes the recent updates to the 1.0.x releases so that poetry is installed with a version of poetry-core that addresses this issue?
I have searched the issues of this repo and believe that this is not a duplicate.
I have searched the documentation and believe that my question is not covered.
The text was updated successfully, but these errors were encountered:
My question is: would it be possible to release 1.1.0a7 that includes the recent updates to the 1.0.x releases so that poetry is installed with a version of poetry-core that addresses this issue?
Resolved by python-poetry/poetry-core#289. The pre-release is built from master branch which should include all fixes of 1.0 branch (and many more).
However, the issue you mention is still open. (By the way, if you want to link a PR from poetry-core, you have to add the prefix python-poetry/poetry-core. I was a little confused for a moment as to what the two Issues were supposed to have to do with each other. 😉)
Hi,
I'm dealing with #4523 across quite a few
poetry
projects. The problem appeared to be some regression betweenpoetry-core
1.0.4 and 1.0.5. Pinning thepoetry
client'spoetry-core==1.0.4
seems to work in the short-term, but I'm not crazy about the hack/patch.poetry
itself depends onpoetry-core^1.1.0a6
, which was released on July 30th, 2021, when the latest1.0.x
release was1.0.3
on April 2021. Since then, the1.0.x
releases have seen updates up to1.0.7
, notably where1.0.6
claims to have fixed this (via #207).poetry/pyproject.toml
Line 37 in e123518
My question is: would it be possible to release
1.1.0a7
that includes the recent updates to the1.0.x
releases so thatpoetry
is installed with a version ofpoetry-core
that addresses this issue?The text was updated successfully, but these errors were encountered: