| Description | Running the extension wizard on Windows from the Git Bash prompt provided by Git for Windows (https://git-for-windows.github.io/) gives the following error:
john@michael MINGW64 /f/3DSlicer/SuperBuild/Slicer-build
$ bin/slicerExtensionWizard
Traceback (most recent call last):
File "F:/3DSlicer/SuperBuild/Slicer-build/libexec/ExtensionWizard.py", line 10, in <module>
w.execute()
File "F:\3DSlicer\SuperBuild\Slicer-build\bin\Python\SlicerWizard\ExtensionWizard.py", line 715, in execute
self._execute(args if len(args) else None)
File "F:\3DSlicer\SuperBuild\Slicer-build\bin\Python\SlicerWizard\ExtensionWizard.py", line 664, in _execute
if args.publish:
AttributeError: 'Namespace' object has no attribute 'publish'
As reported on mailing list:
http://slicer-users.65878.n3.nabble.com/A-problem-when-I-try-to-invoke-ExtensionWizard-td4030358.html
(Archive link on http://massmail.spl.harvard.edu/mailman/listinfo/slicer-users gives 404?)
The specific AttributeError results from a minor bug in the ExtensionWizard itself. But the root cause is that the PATH that reaches Python is incorrect, so Python doesn't find required DLLs. |
|---|
| Additional Information | The following call in slicerExtensionWizard sets the PATH, along with other environment variables:
eval $("F:/3DSlicer/SuperBuild/Slicer-build/Slicer" --launcher-show-set-environment-commands)
The MSYS2 environment that Git for Windows uses converts the contents of PATH to Unix format when launching a process, such as when slicerExtensionWizard runs Python. That conversion corrupts the PATH. A Windows path like "C:/foo/bar" is converted to two separate paths (/C and /c/foo/bar) because MSYS2 considers the colon as a separator.
This wasn't a problem with the older Git Bash, provided by msysGit, because its MSYS didn't perform this conversion.
MSYS2 provides some control over this path conversion for command-line arguments (MSYS2_ARG_CONV_EXCL, MSYS_NO_PATHCONV), but there is no such control for the PATH environment variable. |
|---|
