Skip to content

Consider not using 'HOME' as an environment variable #1219

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

Open
ke5fx opened this issue May 2, 2023 · 1 comment
Open

Consider not using 'HOME' as an environment variable #1219

ke5fx opened this issue May 2, 2023 · 1 comment

Comments

@ke5fx
Copy link

ke5fx commented May 2, 2023

It seems WinPython has chosen to use the environment variable name HOME to point to its settings folder (HOME=c::\WinPython-31090\settings in my Win10 installation). It doesn't require much imagination to see how using such a generic variable name is asking for trouble with respect to other applications that unfortunately chose to do the same thing (CadSoft's EAGLE, in my case.)

If it's feasible to revisit this decision, I'd suggest either using the existing $HOMEPATH variable (e.g., $HOMEPATH\WinPython\settings) or creating a WINPYHOME or similar environment variable for your own use.

@BevanBroun
Copy link

I have the same issue with this. I launch from powershell and my workaround is to modify a few lines in WinPython_PS_Prompt.ps1

27c27
< $env:HOME = "$env:WINPYDIRBASE\settings"

$env:HOME_BB = "$env:WINPYDIRBASE\settings"
33c33
< $env:JUPYTER_DATA_DIR = "$env:HOME"


$env:JUPYTER_DATA_DIR = "$env:HOME_BB"
108c108
< $env:tmp_pyz = "$env:HOME.pyzo"


$env:tmp_pyz = "$env:HOME_BB.pyzo"
110c110
< $env:tmp_pyz = "$env:HOME.pyzo\config.ssdf"


$env:tmp_pyz = "$env:HOME_BB.pyzo\config.ssdf"

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

No branches or pull requests

3 participants