-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
--exists-action
's w
flag, is interpretted as a request for a package called w
when using pipenv install -e "."
#2326
Comments
Sorry for the confusing issue. The exists-action should probably be moved to an environment variable, but in the meantime, don't surround the Thanks for reporting! |
related: #2279 (another reason to implement this) |
thanks @techalchemy , but I tried with and without quotation marks already and no dice! :( |
Oh boy that’s very odd. And if you leave out the |
yeah, sorry 😞 removed |
@techalchemy what is bizarre is that it has no problems whatsoever, when i try to install the same package from a DIFFERENT directory, e.g. when I make a directory I tried |
@techalchemy I think I found the problem.. I only get the error when I replace the url for our private [[source]] with Not sure why, but thank god I can finally move on! Thanks for your help. |
- Fixes #2326 Signed-off-by: Dan Ryan <[email protected]>
Been using pipenv for months, never ran into this before:
run
pipenv install -e "."
seems to result in the request/collection of some random package calledw
(Wallace!!) that's on pypi!!!!As far as I can tell the reason why it searches for "w" is the
--exists-action
option in core.py (line 1488).(it doesn't help that the authors of
Wallace
attempt to open arequirements.txt
file in theirsetup.py
)Verbose output:
(ubuntu 18.04, python 2.7.15, pip 10.0.1, pipenv 2018-05-18)
The text was updated successfully, but these errors were encountered: