[Debian-med-packaging] Bug#652489: NameError: global name 'ViewerFrameworkGUI' is not defined

Andreas Tille andreas at an3as.eu
Sun Dec 18 15:41:27 UTC 2011


On Sun, Dec 18, 2011 at 11:24:50PM +0800, lina wrote:
> $ cat /usr/lib/python2.7/dist-packages/ViewerFramework/VF.py | grep
> ViewerFrameworkGUI
>     from ViewerFramework.VFGUI import ViewerFrameworkGUI
>             self.GUI = ViewerFrameworkGUI(self, title=title,
> 
> see there is a ViewerFrameworkGUI in the VF.py script.
> 
> well... before due to historical reason, when you have python2.6
> there, there is a VF.py
> this one use ViewerFramework(self, ...) which why the wrong message
> saying: global name 'ViewerFrameworkGUI' is not defined
> 
> VF.py which is linked to /usr/share/pyshared/ViewerFramework/VF.py

Yes.  It is the Python debhelper method which installs the following:

$ apt-file search "/VF.py"
mgltools-viewerframework: /usr/lib/python2.6/dist-packages/ViewerFramework/VF.py
mgltools-viewerframework: /usr/lib/python2.7/dist-packages/ViewerFramework/VF.py
mgltools-viewerframework: /usr/share/pyshared/ViewerFramework/VF.py

where the Python modules will be byte compiled for each Python version
separately.  So I can not really see a reason why in your case the
script failed.
 
> I guess it's related to the update of VF.py (might be wrong)
> 
> >
> > Sorry, I can not reproduce the problem on my machine and I would like
> > to see the problem reasonable understood before closing the bug.
> you may remove all python and tried to monitor the VF.py under
> /usr/share/pyshared/ViewerFramework/ when some version of python was
> installed.

>From my point of view this will end up in wild guessing.  The error
message you sended seemed not related to Python 2.6 and removing Python
2.6 as a fix seemed strange.  In principle autodocktools should work
with both Python 2.6 and 2.7 and the installation method described above
guarantees this for a lot of Python modules in Debian so we can assume
that this works reliable.

I'd be tempted to close this bug because I can not reproduce it and it
should be solved on your machine as well.  Or will it come back once
you reinstall python2.6?

Kind regards

       Andreas.

-- 
http://fam-tille.de





More information about the Debian-med-packaging mailing list