Skip to content
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

Document semantics and syntax of version specification in VCS URL. #4181

Closed
piotr-dobrogost opened this issue Dec 13, 2016 · 3 comments
Closed
Labels
auto-locked Outdated issues that have been locked by automation type: docs Documentation related

Comments

@piotr-dobrogost
Copy link

Currently at VCS Support one reads (emphasis mine):

The "project name" component of the url suffix "egg=<project name>-<version>" is used by pip in its dependency logic to identify the project prior to pip downloading and analyzing the metadata. The optional "version" component of the egg name is not functionally important. It merely provides a human-readable clue as to what version is in use.

However looking at examples at jazzband/pip-tools#372 (comment) specifying version number influences pip's behavior of install command noticeably. Please notice that these examples use egg=<project name>==<version> syntax which is not mentioned at all in the VCS Support section of documentation.

Documentation should give answers to how does egg=<project name>-<version> relate to egg=<project name>==<version> and what is the semantics of specifying version in either form.

@pradyunsg pradyunsg added the type: docs Documentation related label Jun 30, 2017
@chrahunt
Copy link
Member

IMO we should deprecate this syntax (with some long deprecation period) and refer to the PEP 440 direct URL syntax instead.

@pradyunsg
Copy link
Member

#egg=<something> -- yep. Sounds like a good idea to me. :)

@xavfernandez
Copy link
Member

Regarding the initial documentation issue, it should have been closed via #4174 & #5888 .
Regarding the #egg syntax deprecation, #1289 should be the right issue so I'm closing this one.

@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Dec 11, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Dec 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation type: docs Documentation related
Projects
None yet
Development

No branches or pull requests

4 participants