-
-
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
guide: add example to install from git branch or tag #2685
Comments
We don't control that website, unfortunately, but if it's not become clear to you yet you can do this from the command line with |
appending i tried |
such examples could be present in this project |
Yeah that is why we left this issue opened. We can’t control what other websites write in their user guides. |
Also it took me a while to figure out you needed to escape & in the url for subdirectory. |
you need to escape
|
@glensc you are right, for some reason I thought same command was working with pip but not with pipenv, I must be using quotes with pip |
I think we are all set on this front now (merged #2702) -- thanks for opening the issue and thanks for the helpful back and forth all! |
#2702 is excellent, exactly what was missing! |
This is how I solved it,
|
How to checkout a tag and install from https://github.com/ccxt/ccxt. Also it is a js/php/py repo with python subfolder? |
If you want to install via ssh (say, for a private repo), you'll need to modify the GitHub ssh url as follows:
Correct: And the install looks like:
Otherwise you'll get a very long install process followed by the cryptic error: pipenv.patched.notpip._internal.exceptions.InstallationError: Command "git clone -q ssh://git@github.com:coltonbh/my-package.git /var/folders/w2/rkn1bm3d3ndclys0f81clbfw0000gn/T/requirementslib5mkvyj4m/mypgk" failed with error code 128 in None |
Is your feature request related to a problem? Please describe.
https://realpython.com/pipenv-guide/#example-usage
please add here example how to add package from git branch "develop" or tag "1.0.0". it is not obvious for persons who started to use pipenv and not familiar with python ecosystem.
The text was updated successfully, but these errors were encountered: