Closed chardigio closed 2 years ago
This is not unexpected -- our current situation with unpinned poetry-core
versions is less than ideal, but the reality of our prereleases is only the latest version is supported. Because an improved pre-release poetry-core
has been released to support a new Poetry pre-release, this incompatibility has occurred. The solution is to update to Poetry 1.2.0b2 and validate it works in your environment ahead of a full release.
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
Sorry, a bit sparse on details here, but wanted to report a bug (that is probably rare, so no hard feelings if you close this without action, especially since I have a workaround).
I've been installing poetry via pip
And today I found my application was hard down because poetry was simply no-op'ing (with no output, even with a -vvv) at the
step of my deploy pipeline.
I eventually discovered this was due to poetry-core drifting to 1.1.0b2 without me knowing.
I pinned poetry-core back to 1.1.0a7 and everything went back to normal as expected.