-
Notifications
You must be signed in to change notification settings - Fork 416
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
Introduce a new env variable to allow spaces in home path #1446
Conversation
@huxuan if you have the time, could you please verify that the windows example for moving the pipx install location actually works? Or maybe even translate it to powershell? |
Gotcha, will take a look later. |
Verified and translated! PTAL |
92e0f10
to
d3fefee
Compare
Sorry had to add just one small change to make sure spaces in the paths are not a problem when using bash. |
looks like the double quotes are also needed for the dirs and $NEW_LOCATION in powershell to work with spaces in paths. |
e33ee59
to
8d9ac27
Compare
Co-authored-by: Xuan (Sean) Hu <i@huxuan.org>
Co-authored-by: Xuan (Sean) Hu <i@huxuan.org>
018af10
to
e8d1bf0
Compare
Co-authored-by: chrysle <96722107+chrysle@users.noreply.github.com>
changelog.d/
(if the patch affects the end users)Summary of changes
Introduces an environment variable to silence the warning for having a space in the pipx home path.
Improves the docs on how to troubleshoot the warning and move the pipx installation location in general. This makes the discussion I created a while ago redundant.
Resolves #1320
Test plan
Tested by running