Skip to content

Add support for hg-git (e.g. pip install -e hg+git+ssh://git@....) #224

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

Closed
vbabiy opened this issue Mar 15, 2011 · 4 comments
Closed

Add support for hg-git (e.g. pip install -e hg+git+ssh://git@....) #224

vbabiy opened this issue Mar 15, 2011 · 4 comments
Labels
auto-locked Outdated issues that have been locked by automation

Comments

@vbabiy
Copy link
Contributor

vbabiy commented Mar 15, 2011

I'm using mercurial to access git repositories, but I can not get pip working with git repository accessed by ssh.

pip install -e hg+git://github.com/... - works :)

pip install -e hg+git+ssh://... - almost works, but it tries to clone repository with #egg=sleekxmpp. See below:

#!shell
pip install -e hg+git+ssh://[email protected]:andyhelp/SleekXMPP.git#egg=sleekxmpp
Obtaining sleekxmpp from hg+git+ssh://[email protected]:andyhelp/SleekXMPP.git#egg=sleekxmpp
  Cloning hg git+ssh://[email protected]:andyhelp/SleekXMPP.git#egg=sleekxmpp to ./sleekxmpp
abort: ref egg=sleekxmpp not found on remote server

I guess that pip is confused by two + signs used to specify url?


@vbabiy
Copy link
Contributor Author

vbabiy commented Mar 15, 2011

  • Changed type from enhancement to proposal.

Original Comment By: andyhelp

@pnasrat
Copy link
Contributor

pnasrat commented May 1, 2011

I'm not convinced that we want to support vcs bridging to vcs functionality, we'd endup having to support git+{cvs,darcs,hg,...}. for example. This seems as if it adds complexity, pip is inherently a package manager and should support the upstream package repository types, but this workflow seems quite corner case to me (ie use only one vcs for everything).

@jezdez, @carljm - any thoughts?

@carljm
Copy link
Contributor

carljm commented May 1, 2011

I agree, supporting every possible vcs-to-vcs bridge natively is out of scope for pip. Pip can access git repositories using git - that's sufficient.

@carljm carljm closed this as completed May 1, 2011
@jezdez
Copy link
Member

jezdez commented May 1, 2011

Agreed.

@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 6, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 6, 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
Projects
None yet
Development

No branches or pull requests

4 participants