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.

Sign up for GitHub

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

Jump to bottom

Allow expansion of "~" in paths listed in pip.conf #980

Closed
rbarrois opened this issue Jun 5, 2013 · 3 comments · Fixed by #7534
Closed

Allow expansion of "~" in paths listed in pip.conf #980

rbarrois opened this issue Jun 5, 2013 · 3 comments · Fixed by #7534
Labels
auto-locked Outdated issues that have been locked by automation C: configuration Configuration management and loading state: awaiting PR Feature discussed, PR is needed type: enhancement Improvements to functionality

Comments

@rbarrois
Copy link

rbarrois commented Jun 5, 2013

It would be great to be able to set cert = ~/.pip/cacert.pem in .pip/pip.conf, for instance using expanduser.

I'll craft a pull request soon.
@rbarrois rbarrois mentioned this issue Jun 5, 2013
Closed
@ariddell
Copy link

ariddell commented Jun 6, 2013

and in commands as well, e.g.: pip wheel --wheel-dir=~/.pip_wheelhouse pyzmq

@dstufft
Copy link
Member

dstufft commented Mar 22, 2017

Ideally this should be implemented by adding a new optparse type or something similar that will solve it for all paths and not adhoc uses of os.path.expanduser.

@dstufft dstufft mentioned this issue Mar 22, 2017
Closed
@cjerdonek cjerdonek mentioned this issue Jan 28, 2019
Closed
@chrahunt chrahunt added the state: awaiting PR Feature discussed, PR is needed label Sep 15, 2019
@chrahunt chrahunt mentioned this issue Dec 27, 2019
Merged
@uranusjr uranusjr mentioned this issue Jan 1, 2020
Merged
@rbarrois
Copy link
Author

@uranusjr thanks for fixing this! I really appreciate your help :)

@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Feb 21, 2020
@lock lock bot locked as resolved and limited conversation to collaborators Feb 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
auto-locked Outdated issues that have been locked by automation C: configuration Configuration management and loading state: awaiting PR Feature discussed, PR is needed type: enhancement Improvements to functionality
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Custom optparse.Option type that calls expanduser uranusjr/pip
4 participants
@ariddell @dstufft @rbarrois @chrahunt