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
PythonSlicer with extension paths #4603
Milestone
Comments
@jcfr is this still relevant? |
@jcfr please close or retarget |
This should be fixed implementing the change discussed in https://discourse.slicer.org/t/slicer-no-main-window-python-script-in-windows-command-prompt-not-working/6481/26?u=jcfr |
jcfr
added a commit
to jcfr/Slicer
that referenced
this issue
May 5, 2020
This commit updates the configuration of the launcher to ensure the settings needed to lookup the user revision settings are set. The user revision settings contain the extension settings like Paths, LibraryPaths and EnvironmentVariables. See https://discourse.slicer.org/t/slicer-no-main-window-python-script-in-windows-command-prompt-not-working/6481/26 Fixes Slicer#4603
jcfr
added a commit
to jcfr/Slicer
that referenced
this issue
May 5, 2020
This commit updates the configuration of the launcher to ensure the settings needed to lookup the user revision settings are set. The user revision settings contain the extension settings like Paths, LibraryPaths and EnvironmentVariables. See https://discourse.slicer.org/t/slicer-no-main-window-python-script-in-windows-command-prompt-not-working/6481/26 Fixes Slicer#4603
jcfr
added a commit
to jcfr/Slicer
that referenced
this issue
Nov 26, 2021
This commit updates the configuration of the launcher to ensure the settings needed to lookup the user revision settings are set. The user revision settings contain the extension settings like Paths, LibraryPaths and EnvironmentVariables. See https://discourse.slicer.org/t/slicer-no-main-window-python-script-in-windows-command-prompt-not-working/6481/26 Fixes Slicer#4603
jcfr
added a commit
to jcfr/Slicer
that referenced
this issue
Nov 26, 2021
This commit updates the configuration of the launcher to ensure the settings needed to lookup the user revision settings are set. The user revision settings contain the extension settings like Paths, LibraryPaths and EnvironmentVariables. See https://discourse.slicer.org/t/slicer-no-main-window-python-script-in-windows-command-prompt-not-working/6481/26 Fixes Slicer#4603
jcfr
added a commit
that referenced
this issue
Nov 26, 2021
This commit updates the configuration of the launcher to ensure the settings needed to lookup the user revision settings are set. The user revision settings contain the extension settings like Paths, LibraryPaths and EnvironmentVariables. See https://discourse.slicer.org/t/slicer-no-main-window-python-script-in-windows-command-prompt-not-working/6481/26 Fixes #4603
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
The text was updated successfully, but these errors were encountered: