poetry: Export fails after upgrading poetry to version 1.1.0
- 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: Linux (archlinux and CentOS 7).
- Poetry version: 1.1.0
- Link of a Gist with the contents of your pyproject.toml file: https://gist.github.com/iksteen/2464d767a57ed034af25956264be2694
Issue
After upgrading poetry from 1.0.0 to 1.1.0, poetry export -frequirements.txt results in the following exception when using a poetry.lock file created by an earlier version: https://gist.github.com/iksteen/bd4fd24e2b79e0f0644461fe501297d4
Running poetry lock using poetry 1.1.0 fixes the problem.
While not a huge issue, this currently frustrates our CI strategy as we have an assumption there that installing poetry>=1.0,<2.0 would be sufficient to guard against incompatibilities of poetry updates. Currently we have quite a few PRs on several projects that suddenly won’t build in the CI anymore.
While this seems similar to https://github.com/python-poetry/poetry/issues/3018, the conditions under which this occurs differ significantly (#3018 is also triggered after running poetry lock).
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 12
- Comments: 18 (13 by maintainers)
We’ve also noticed the same issue in all our builds 😭
We really do appreciate that this is an issue. However, please do bear with us. The various variables to consider in how people are using poetry is sometimes hard to keep track of. Especially when we need to make critical changes to to the resolver to expand both reliability and supported scenarios. Again, thank you for using poetry, and providing detailed bug reports.
Same. Also the error gets printed to stdout, which is piped to the requirements.txt output. I guess I’ll open an issue about that (edit: #3025)