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 quite confused by this error. I'm prevented of installing my project even though my configuration file is perfectly valid.
The error is also very much not explicit. I had to manually modify the poetry source code to find out which package was responsible for this error. (It was some package installed with pip install -e).
Looking at other github issue (#4176), it seems that I'm not the first to have similar issue. Like pip, poetry should ignore non-standard packages, rather than failing. Or at minima raise more explicit error messages.
The text was updated successfully, but these errors were encountered:
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 (
-vvv
option).OS version and name: MacOS
Poetry version: 1.2.0a
Issue
I have a dummy poetry file:
I'm trying to install this file globally (as this is a
poetry
plugin)poetry config virtualenvs.create false poetry install
However this fail with:
Full stacktrace: https://gist.github.com/Conchylicultor/d868433147613a1e9cd89d0d15f6b107
I'm quite confused by this error. I'm prevented of installing my project even though my configuration file is perfectly valid.
The error is also very much not explicit. I had to manually modify the poetry source code to find out which package was responsible for this error. (It was some package installed with
pip install -e
).Somehow I think poetry try to parse the package installed on my system. I checked with
pip freeze
that no package has3.2.1
version (https://gist.github.com/Conchylicultor/a0922af93f734de3368208f9044536ee).Looking at other github issue (#4176), it seems that I'm not the first to have similar issue. Like
pip
, poetry should ignore non-standard packages, rather than failing. Or at minima raise more explicit error messages.The text was updated successfully, but these errors were encountered: