View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0003387Slicer4Core: Scripting (Wrapping, Python)public2013-09-10 12:322014-03-06 05:28
Reporterfedorov Assigned Topieper  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Product VersionSlicer 4.3.0 
Target VersionSlicer 4.3.1Fixed in VersionSlicer 4.3.1 
Summary0003387: SurfaceToolBox fail to import in release package
Description

Discussion: http://slicer-devel.65872.n3.nabble.com/Startup-error-in-4-3-explicit-import-string-is-required-tt4029903.html

From Andriy:

Hi,

I compiled Slicer from the current trunk, and I have the following
error on startup:

Traceback (most recent call last):
File "/Users/fedorov/local/builds/Slicer4-Release/Slicer-build/lib/Slicer-4.3/qt-scripted-modules/SurfaceToolbox.py",
line 11, in init
parent.helpText = string.Template("""

It appears that in the past 'string' was imported somewhere else, but
now explicit import is required?

I have not done a clean build, perhaps this could have somehow caused this.

AF

Additional Information

From Nicole: Get that message when starting with --disable-cli-modules

TagsNo tags attached.

Activities

pieper

pieper

2013-09-10 13:25

administrator   ~0009925

I did a fresh re-build on mac and could not replicate the issue. It may be an issue related to other modules you have installed?

But it should be an easy fix anyway - can you try adding 'import string' before line 11 of SurfaceToolbox.py and see if that fixes it?
fedorov

fedorov

2013-09-11 05:34

developer   ~0009926

The error is not in release package - it is in a local build. I checked there is no error in the package.

Steve: note that Paul reports the same issue with a fresh build: http://slicer-devel.65872.n3.nabble.com/Startup-error-in-4-3-explicit-import-string-is-required-td4029903.html

Adding import string fixes it, but then I had the same error in MultiVolumeExplorer module, until I added that import.

I will change the priority to minor, since it is not present in the package release, not consistently reproducible, and is easy to fix for developers.
pieper

pieper

2013-09-11 05:48

administrator   ~0009928

Thanks for testing this.

The fresh build I did was a local developer build so it should replicate your situation exactly (hence the mystery).

Do you have custom module paths set?
fedorov

fedorov

2013-09-12 11:47

developer   ~0009949

Steve: I do have custom paths, if I remove them, the error does not go away.
jcfr

jcfr

2013-09-17 12:19

administrator   ~0009976

Fixed in r22433
See http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=22433
jcfr

jcfr

2014-03-06 05:24

administrator   ~0011201

Closing resolved issues that have not been updated in more than 3 months

Issue History

Date Modified Username Field Change
2013-09-10 12:32 jcfr New Issue
2013-09-10 12:32 jcfr Status new => assigned
2013-09-10 12:32 jcfr Assigned To => jcfr
2013-09-10 12:32 jcfr Reporter jcfr => fedorov
2013-09-10 12:32 jcfr Assigned To jcfr => pieper
2013-09-10 12:32 jcfr Target Version => Slicer 4.3.1
2013-09-10 12:32 jcfr Severity minor => major
2013-09-10 13:25 pieper Note Added: 0009925
2013-09-11 05:34 fedorov Note Added: 0009926
2013-09-11 05:34 fedorov Severity major => minor
2013-09-11 05:48 pieper Note Added: 0009928
2013-09-12 11:47 fedorov Note Added: 0009949
2013-09-17 12:19 jcfr Note Added: 0009976
2013-09-17 12:19 jcfr Status assigned => resolved
2013-09-17 12:19 jcfr Fixed in Version => Slicer 4.3.1
2013-09-17 12:19 jcfr Resolution open => fixed
2014-03-06 05:24 jcfr Note Added: 0011201
2014-03-06 05:28 jcfr Status resolved => closed