-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Direct references are not working #4447
Comments
Support for this syntax was added in #4175, which was merged after |
The release notes for 8.1.2 (2016-05-10) report something different:
Also how do you explain that
or
work without a problem? Just for this test repo it doesn't work. The only difference I can spot is that the former ones are all published on PyPi while the latter isn't. But direct references are meant to support packages which are not published on PyPi, aren't they? Or does pip use some kind of fallback on PyPi in case it doesn't understand this syntax? |
The release notes here are a bit confusing and might better read:
Meaning it is only referring to https://www.python.org/dev/peps/pep-0508/#environment-markers and not to the The reason |
As @di pointed out, this support will be there as a part of the next release of pip. On that note, I'm closing this issue. :)
I'll make a PR fixing that. :) |
Description:
PEP 440 introduces the usage of direct references. The pip release notes report to have implemented this PEP (with some subsequent minor modifications).
However I can't get this feature to work. Particularly I wanted to use it in the
install_requires
section of asetup.py
script. I tried all the different variations that are used as examples in the PEP specification however none of them worked. The response always is:I also tried install the package directly with pip on the CLI however this gave me the same error:
What I've run:
I've tried all the variations of examples that are given in the PEP 440 specification. Here's a collection of a few. Using git:
Using an archive:
However I've also verified that the following works:
I don't see what's the difference, really. In the former case it's not even attempting to download the repo while the command is similar to the latter case.
The text was updated successfully, but these errors were encountered: