-
Notifications
You must be signed in to change notification settings - Fork 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
replace egg=
with pkg=
#1265
Comments
+10000 |
Hah, yeah! +1 |
or better, maybe we can just get rid of it, see #1289 |
The Python docs tend to use “pkg” for “package”, i.e. a module that contains modules. Using it to mean package/distribution/project name could be ambiguous. |
@merwok it's intending to be consistent with "package meaning #2" I gave in a while back, and let the PUG have 2 meanings for "package". although |
I wouldn't mind |
|
I would recommend |
I like |
thinking it makes since to close this as no fix considering the approval of PEP508. PEP508 paves the way for pip to migrate to the direct reference syntax for VCS urls (https://www.python.org/dev/peps/pep-0440/#direct-references) i.e, this: one detail left hanging though is the use of the |
I think that pip currently drops it https://github.com/pypa/pip/blob/69d9044/pip/req/req_install.py#L1056-L1065 I agree this could be closed. |
If everyone thinks this is resolved - can we please close this? ^.^ |
Yup, |
With the demise of eggs, the "egg=" url fragment syntax is only becoming more obscure.
We could start supporting both "egg=" and a newer "pkg=" format, then eventually deprecate, then remove support for "egg="
Ideally, we'd do this in conjunction with setuptools.
The text was updated successfully, but these errors were encountered: