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

vsc-install asks for credentials when using tox #124

Open
wdpypere opened this issue Dec 23, 2019 · 4 comments
Open

vsc-install asks for credentials when using tox #124

wdpypere opened this issue Dec 23, 2019 · 4 comments

Comments

@wdpypere
Copy link
Contributor

when running tests locally I get:

...
INFO: Searching for vsc-config>=1.31.0
INFO: Doing git clone from ssh://[email protected]/hpcugent/vsc-config.git to /tmp/easy_install-naixMB/vsc-config.git
Enter passphrase for key '/home/wdpypere/.ssh/id_rsa': 

I see no reason why vsc-install should even try to use my SSH keys or passphrases?

@boegel
Copy link
Member

boegel commented Dec 23, 2019

I'm not sure we can avoid this...

Maybe vsc-install should try using https:// before using ssh:// URLs?

@boegel
Copy link
Member

boegel commented Dec 23, 2019

@stdweird Thoughts on this?

@boegel
Copy link
Member

boegel commented Mar 25, 2020

the changes in #143 don't actually fix this, so re-opening...

@boegel boegel reopened this Mar 25, 2020
@boegel
Copy link
Member

boegel commented Sep 16, 2020

This is still a problem, and it also happens when running python setup.py test in repos that depends on a private repo like vsc-config.

Two possible solutions are:

  • manually installing the dependency that is hosted in a private repo into the .eggs.py2 or .eggs.py3 subdirectory, using PYTHONPATH=/path/to/.eggs.py2:$PYTHONPATH python setup.py install --prefix /path/to/.eggs.py2 --install-lib /path/to/.eggs.py2 (the --install-lib is important to avoid installing into a lib/python*/site-packages subdir in the .eggs.py2 dir)
  • for reason just blasting away the .eggs.py* directory and just trying again seems to help too, but perhaps that's due to some caching mechanism, I don't understand how that would suddenly make the private repo accessible when it isn't before

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

No branches or pull requests

2 participants