-
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
Packaging requirements #3307
Packaging requirements #3307
Conversation
114d234
to
39fa956
Compare
39fa956
to
3863d30
Compare
3863d30
to
8122856
Compare
8122856
to
075fbc6
Compare
@@ -361,7 +361,7 @@ def _correct_build_location(self): | |||
def name(self): | |||
if self.req is None: | |||
return None | |||
return native_str(self.req.project_name) | |||
return native_str(pkg_resources.safe_name(self.req.name)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe use packaging.utils.canonicalize_name
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, but canonicalize_name also lowercases the result, which is bad, since it turns up in the output of pip, which breaks the test suite, and also impacts uninstallability.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How does it impact uninstallability ?
075fbc6
to
47de02f
Compare
47de02f
to
f5aa978
Compare
f5aa978
to
8e236dd
Compare
I think I am seeing the same issue, with a local devpi-server and the module zope.deprecation
Then when updating pip only:
However, it seems to work when going straight to the pypi server:
Is it possible that the devpi-server could just work with a different configuration? Why could the bases fail if the versions do exist and work with pip 8.1.1? The devpi-server is the latest:
|
devpi version 4 will include working pep 503 support and will need a database migration |
Stop using pkg_resources.Requirements inside pip to represent parsed requirements, instead make use of packaging.requirements.Requirement to do so.