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

Can't install zope-component even though it's on PyPI #5991

Closed
wimglenn opened this issue Nov 7, 2018 · 2 comments
Closed

Can't install zope-component even though it's on PyPI #5991

wimglenn opened this issue Nov 7, 2018 · 2 comments
Labels
auto-locked Outdated issues that have been locked by automation resolution: duplicate Duplicate of an existing issue/PR

Comments

@wimglenn
Copy link
Contributor

wimglenn commented Nov 7, 2018

$ pip install zope-component==4.2.0 
Collecting zope-component==4.2.0
  Could not find a version that satisfies the requirement zope-component==4.2.0 (from versions: 4.3.0, 4.4.0, 4.4.1, 4.5)
No matching distribution found for zope-component==4.2.0

Environment

  • pip version: 18.1
  • Python version: 3.7.1
  • OS: Linux

Description

pip can not install zope-component using the canonical name even though it is clearly present in the index --> see https://pypi.org/simple/zope-component/

For some reason, pip is still able to resolve other versions like 4.3.0. Perhaps because they have wheels up, not just sdist.

Expected behavior

pip install zope-component==4.2.0 and pip install zope.component==4.2.0 should do the same thing.

>>> from packaging.utils import canonicalize_name
>>> canonicalize_name('zope.component')
'zope-component'

I just use zope as an example, same issue probably exists for other namespace packages.

@cjerdonek cjerdonek added the resolution: duplicate Duplicate of an existing issue/PR label Nov 8, 2018
@cjerdonek
Copy link
Member

I believe this is a duplicate of the following resolved issue: #5870

Feel free to re-open if not.

@lock
Copy link

lock bot commented May 31, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot added the auto-locked Outdated issues that have been locked by automation label May 31, 2019
@lock lock bot locked as resolved and limited conversation to collaborators May 31, 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 resolution: duplicate Duplicate of an existing issue/PR
Projects
None yet
Development

No branches or pull requests

2 participants