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

Pipenv prefers a local package with the same name #4120

Closed
andreif opened this issue Jan 30, 2020 · 1 comment
Closed

Pipenv prefers a local package with the same name #4120

andreif opened this issue Jan 30, 2020 · 1 comment
Labels

Comments

@andreif
Copy link

andreif commented Jan 30, 2020

Issue description

I have a subfolder with name "requests" that contains an empty "setup.py". I try to import the real requests package from PyPI by running pipenv install requests

Expected result

I expect the real requests to be installed.

Actual result

Pipenv tries to install the local requests package. Pipenv should install local packages if I provide a path to it, not just the name, e.g. pipenv install ./requests.

Steps to replicate

mkdir requests
touch requests/setup.py
pipenv install requests
@uranusjr
Copy link
Member

This has been identified as a bug in pip, and will be fixed (pypa/pip#7955) by the next pip release scheduled later this month. I will close this for now since the diagnose (if correct) puts the solution out of Pipenv’s reach. Feel free to reopen if this still happens with pip 20.1 (i.e. indicates the diagnose was wrong).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants