Today’s nightly windows Slicer starts, but all scripted modules are broken. Today’s nightly on mac works fine for me, as does 4.8.1 on the same windows machine. The first error message is: >>> import vtk Traceback (most recent call last): File "<console>", line 1, in <module> ImportError: No mo…

Since nothing was expected to change for the current nightly, I suspect r26834 introduced the regression. Cc: @adamrankin

I had the same issue and could fix it locally by modifying SlicerLauncherSettings.ini. I had to add VTK Python packages location <APPLAUNCHER_DIR>/bin/Lib/site-packages to section [PYTHONPATH]. It would be great if somebody could fix the ini file generation.

This is beyond my level of knowledge. If Andras’ fix is the correct one, I can implement the change.

I’m not sure if the correct solution is to add/change paths in launcher settings (by changing External_VTKv9.cmake) or change VTK configuration to deploy site-packages to a different folder. @jcfr Could you advise?

I can confirm the fix from Andras works. The SlicerLauncherSettings.ini file is in the bin directory and in addition to adding the line 12\path=<APPLAUNCHER_DIR>/bin/Lib/site-packages you need to increment the last line of the section to size=12. Other notes: the nightly crashes when started over …

[image] pieper: Today’s nightly windows Slicer starts, but all scripted modules are broken @pieper Look like you meant “building the current trunk with Qt5 and VTK9 enabled” ? (there is no bin/Lib/site-packages directory in the current nightly windows package)

@jcfr I just downloaded and installed 4.9.0-2018-01-17 and I have a bin/Lib/site-packages: [image]

@pieper This is very strange, the vtkmodules package is not expected to exist in the current nightly. It also doesn’t exist in the install tree used to create the package: [Screenshot from 2018-01-18 10-39-48]

@pieper I confirm that after installing the nightly package (that was built on the factory), it is different from what you have. I suspect the factory.perklab site maintained by @lassoan is uploading the installer and that would explain what you observed

factory.perklab has not been uploading packages for a while (temporarily disabled). I (and probably Steve as well) use the local package folder - c:\D\S4R\Slicer-build\_CPack_Packages\win-amd64\NSIS\Slicer-4.9.0-2018-01-17-win-amd64.

Vtk python does not import on today's windows nightly

Development

Topic		Replies	Views
2018-10-15 Windows nightly build "unable to import VTK" Support	2	784	October 16, 2018
Error creating a module VMTK extensions-manager , vtk , vmtk , module , error	15	1000	November 8, 2022
Numerous errors on startup with today's nightly on mac Support dicombrowser	1	711	October 6, 2020
VMTK Extension Problem Support vmtk	1	1474	September 25, 2020
Vtkvmtk module is not loaded Please help Support	1	400	December 1, 2023

Vtk python does not import on today's windows nightly

Related topics