-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inconsitent requirements on the package name parameters for add
#646
Comments
Just wanted to confirm I am also having this issue trying to install several different wheels (Shapely, Fiona, GDAL).
Everything in the wheel metadata is showing "Shapely":
|
This has been improved n the latest beta release (see #1221 for more information). |
Closed
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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: Ubuntu 18.04
Poetry version: 0.12.8
Link of a Gist with the contents of your pyproject.toml file: https://gist.github.com/nlinker/130181762f02e087e707e08c6f7b81ec
Issue
The bug is: poetry requires the parameter (package name), which is not needed and another value is not accepted.
The origin point, clean virtualenv, the project just created with
new
command, python requirement is changed to"^3.6"
:my_tf
=> I got the complain, that the parameter has wrong value1, 2 and 3 above seems to be contradictory. I'd expect the following one of the behaviors:
poetry add
should deduce the package name from the wheel; orpoetry add
should allow to add the package with the different name, that is passed as the parameterI'm pretty sure it is valid with any wheel, I just used the one from https://github.com/tensorflow/tensorflow/releases
Thanks.
The text was updated successfully, but these errors were encountered: