-
-
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
Unable to install package from private repository #1393
Comments
I just started seeing this problem as well, but when I update the package rather than when I'm installing it. In the
when I run
As you can see there's no I'm sure it used to work. Now I have to manually remove that additional line to keep my |
I am also seeing similar problems. When installing without the
If I install the same package with the
|
@techalchemy This worked properly with pipenv up to version 9 but with pipenv 11 |
@bokhi I'm trying to install a package from a private Bitbucket repository from which you can only clone via SSH, not HTTPS. Pipenv tries to execute |
For some reason, the stack trace is cut off. Here's what I get:
|
That’s not where the problem is but it is actually really helpful. If you use the |
@techalchemy How do you even specify the port with the syntax |
From https://pip.pypa.io/en/stable/reference/pip_install/#git
Naturally if you use an ssh based approach you will need to have a password or a key pair for authentication. You can also use an http based approach which is not going to be impacted by this bug: Please read the pip documentation if you want to know how to interact with vcs repositories. |
I read the pip documentation (the exact page you posted) and it doesn't cover how to specify the port when using this type of URI, which you've suggested as a workaround. That's why I asked. As mentioned above, HTTP access is disabled in our Bitbucket instance. My public key is correctly registered with Bitbucket and normal interaction via git and installation of the package via pip itself work perfectly fine. But no matter what I try, I cannot get pipenv to install the package. The fact that it's asking for a password for git makes me suspect that it's always connecting to the regular SSH server on port 22, not the Bitbucket SSH server on port 7999. Sorry if what I wrote before wasn't clear enough. |
Does simply adding the port like you would to a normal url not work? |
I've tried the following variations:
Both don't work, since in this URL scheme, everything behind the first colon seems to be interpreted as the path. |
A bit of additional info: After the initial installation attempt (
The step I tried to manually change the line to the following:
Running
This time, it at least installs all dependencies of the package correctly before failing to install the package itself (asking for the password). Hope that helps track down the problem. Edit: Manually adding "ssh://" in Pipfile.lock as well makes |
@Moritz90 thanks for the thorough debug, I'll get a fix together for this which will be much easier because of this info |
@techalchemy will this fix also help with the original issue filed? It seems the discussion has shifted slightly regarding SSH specifics. |
yes |
To clarify for everyone since there is confusion apparently: @Moritz90 @clayk - the @hcoura your issue is unrelated, you are not using the correct syntax. You are using |
@techalchemy I guess I wasn't explicit as I was using:
Anyway, I did some more testing here(python 2.7.14 btw) and:
Install package but Lock fails, last message:
adds this line to Pipfile:
Install package but Lock fails, last message:
adds this line to Pipfile:
Installs fine and adds this line to Pipfile:
and everything works fine |
Fixed in master, feel free to try it out and let me know if you continue to have issues |
11.1.0 works for me! Thank you for the quick fix! |
It was quite perplexing when I realized that this error was happening on my laptop but not on a fresh test VM ... thank you for the fix :) |
I'm still having a problem trying to make pipenv install from a private repository over ssh. I may have misunderstood the thread above so forgive me. I'm currently trying to use |
@jamesstidard it’s hard to troubleshoot a problem when you say you’ve done things right but it’s not working — please open an issue and provide logs |
I'm also getting errors trying to install a Python package from a private (Gitlab) Git repository using Pipenv. Describe your environment
Expected resultI expected the package to install and the lockfile to be written. Actual resultWithout the
With the
|
To be sure, this is an error in some newer version of Pipenv. The same Pipfile worked before updating to The error I'm getting is:
Now, when I start virtual environment shell and execute there:
pip installs the package. To reflect on the error:
is a lie. This is not an invalid requirement. This is you failing to parse a valid requirement. |
Kind of strange to accuse an unhandled exception of lying. The exception told you what it had a problem with. Still, this feel like a step in the right direction so I’ll look at it as a positive. |
This error is still present on the latest version of
Even though the egg name is present in the source file. |
@thekashifmalik Please be more constructive. You say it like it’s obvious and simple—why not try extracting this information yourself :) |
@uranusjr What? Is there other information you would like me to include?
The requirement: The command used was The error:
|
I mean, maybe put this in the form of a pull request? Code in GitHub issues doesn’t run as part of Pipenv. |
@uranusjr I'm not sure I follow. I'm suggesting that this Github issue (Unable to install package from private repository) is not resolved on the latest stable version of |
Multiple people above have also reported this. Can we re-open this issue? Is it solved on master and we just need a new PyPI release? |
This issue is quite old and was reported specifically about As to your specific issue, you should check closed issues if possible, we have made a lot of changes and it's hard to remember offhand which ones were done since the last release. Alternatively, you can grab the latest version of pipenv from here and see if your requirements.txt file parses correctly |
hi all, I seem to have the same problem installing from a private repo with sources, and after reading this thread a few times it's not clear to me if there's any solution or workaround. here's the problem I have, starting from an empty pipfile
shows the error in console
(basically having a if I then
I have the same installation error as reported above and no package is installed (i.e. I'm using python 3.6.5 with pip 18.0 and pipenv version 2018.7.1. Any help would be greatly appreciated. |
Yes, we have a fix in master but have not released it -- we have been bogged down with a few other issues, many apologies. If you want to confirm that the fix in the master branch works for you, that would be much appreciated! |
@techalchemy thanks for feedback. I'm not sure I've done this the right way, but I've installed pipenv from git, i.e.
should I try something different instead? |
getting same issue as @grudelsud with master version of pipenv |
Ah yes, I can confirm this is an issue on master, I need to dig into what is going on here |
I was having the same issue described; reverting to version 11.10.4 allowed me to install the git package. |
Sam problem here |
- Fixes #1393 Signed-off-by: Dan Ryan <[email protected]>
I realize this issue is closed, but I have the exact same problem as @grudelsud ( |
@techalchemy have we fixed the issue related to installing from the private GitHub repo? |
I am attempting to install from a private repository. The output indicates the package and dependencies were installed but when pipenv is "Locking [packages] dependencies…"
I receive an error indicating: pip.exceptions.InstallationError: Could not detect requirement name, please specify one with #egg=
Describe your environment
Expected result
I am expecting for the package to install and the lockfile to be written.
Actual result
Steps to replicate
execute pipenv install -e git+ssh://path/to/private/[email protected]#egg=privatepackagename
The text was updated successfully, but these errors were encountered: