-
Notifications
You must be signed in to change notification settings - Fork 151
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
How should a PEP 508 requirement with an URL specifier be handled? #249
Comments
|
Oops, amended... |
PEP 345 is superseded by PEP 566. It's still unclear to me wether |
The consensus seems to be that this is allowed by PEP 566: python/peps#763, so I'll PR the changes. |
benoit-pierre
added a commit
to benoit-pierre/wheel
that referenced
this issue
Aug 28, 2018
Do not strip the URLs. Fix pypa#249.
Closed
agronholm
pushed a commit
that referenced
this issue
Sep 23, 2018
Do not strip the URLs. Fixes #249.
noahp
added a commit
to noahp/stash-pr-stats
that referenced
this issue
Dec 23, 2018
Use wheel >= 0.32.0 for [PEP 508](https://www.python.org/dev/peps/pep-0508/) dependencies. See: * pypa/pip#5736 * pypa/wheel#249 and * https://github.com/pypa/wheel/blob/0.32.0/docs/news.rst#release-notes Fixes #1.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Starting with pip 10.0, requirements with URL specifiers are now supported (as replacement for dependency links).
With the following sample project'
setup.py
:Installing from source work, but looking at the generated wheel metadata:
It works with the following patch:
Unfortunately, this is technically not valid PEP 345 metadata.
The text was updated successfully, but these errors were encountered: