Bug#652489: NameError: global name 'ViewerFrameworkGUI' is not defined

[lina]

On Sun, Dec 18, 2011 at 2:32 AM, lina <lina.l...@gmail.com> wrote:
> Package: autodocktools
> Version: 1.5.6~rc2+cvs.20110926-1
> Severity: serious
>
> Dear Maintainer,
> *** Please consider answering these questions, where appropriate ***
> $ autodocktools
> Run ADT from  /usr/lib/python2.7/dist-packages/AutoDockTools
> Traceback (most recent call last):
>  File "/usr/lib/python2.7/dist-packages/AutoDockTools/__init__.py", line 433, in runADT
>    title=title, withShell= not interactive, verbose=False, gui=gui)
>  File "/usr/lib/python2.7/dist-packages/Pmv/moleculeViewer.py", line 888, in __init__
>    trapExceptions=trapExceptions)
>  File "/usr/lib/python2.7/dist-packages/ViewerFramework/VF.py", line 369, in __init__
>    self.GUI = ViewerFrameworkGUI(self, title=title,
> NameError: global name 'ViewerFrameworkGUI' is not defined
> hit enter to continue
>
> once press enter, the autodocktools interface just disappeared, I mean, terminated.

The problem was solved by uninstall the python2.6 and reinstall the
autodocktools.

Thanks,
>
>
>
> Thanks with best regards,
>
>
> -- System Information:
> Debian Release: wheezy/sid
>  APT prefers testing
>  APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 3.2.0-rc63.2-mj-lina (SMP w/8 CPU cores)
> Locale: LANG=en_SG.UTF-8, LC_CTYPE=en_SG.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
>
> Versions of packages autodocktools depends on:
> ii  mgltools-molkit           1.5.6~rc2+cvs.20110926-1
> ii  mgltools-pmv              1.5.6~rc2+cvs.20110926-1
> ii  mgltools-support          1.5.6~rc2+cvs.20110926-1
> ii  mgltools-viewerframework  1.5.6~rc2+cvs.20110926-1
> ii  mgltools-volume           1.5.6~rc2+cvs.20110926-1
> ii  python                    2.7.2-9
> ii  python-imaging-tk         1.1.7-4
> ii  python2.6                 2.6.7-4
> ii  python2.7                 2.7.2-8
>
> Versions of packages autodocktools recommends:
> ii  mgltools-pyautodock   1.5.6~rc2+cvs.20110926-1
> ii  mgltools-utpackages   1.5.6~rc2+cvs.20110926-1
> ii  mgltools-webservices  1.5.6~rc2+cvs.20110926-1
>
> Versions of packages autodocktools suggests:
> pn  autodock       4.2.3-2
> pn  autodock-vina  1.1.2-2
> pn  ballview       <none>
> pn  mgltools-cadd  <none>
>
> -- no debconf information
>
>



--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

[Andreas Tille]

Hi,

On Sun, Dec 18, 2011 at 01:59:06PM +0800, lina wrote:
> On Sun, Dec 18, 2011 at 2:32 AM, lina <lina.l...@gmail.com> wrote:
> > Package: autodocktools
> > Version: 1.5.6~rc2+cvs.20110926-1
> > Severity: serious
> >
> > Dear Maintainer,
> > *** Please consider answering these questions, where appropriate ***
> > $ autodocktools
> > Run ADT from  /usr/lib/python2.7/dist-packages/AutoDockTools
> > Traceback (most recent call last):
> >  File "/usr/lib/python2.7/dist-packages/AutoDockTools/__init__.py", line 433, in runADT
> >    title=title, withShell= not interactive, verbose=False, gui=gui)
> >  File "/usr/lib/python2.7/dist-packages/Pmv/moleculeViewer.py", line 888, in __init__
> >    trapExceptions=trapExceptions)
> >  File "/usr/lib/python2.7/dist-packages/ViewerFramework/VF.py", line 369, in __init__
> >    self.GUI = ViewerFrameworkGUI(self, title=title,
> > NameError: global name 'ViewerFrameworkGUI' is not defined
> > hit enter to continue
> >
> > once press enter, the autodocktools interface just disappeared, I mean, terminated.
>
> The problem was solved by uninstall the python2.6 and reinstall the
> autodocktools.

Thanks for this additional information. However, I admit I do not
exactly know how to prevent this problem for the future. Do you think
that a strict Dependency from python2.7 only would help?

Sorry, I can not reproduce the problem on my machine and I would like
to see the problem reasonable understood before closing the bug.

Kind regards

Andreas.


--
http://fam-tille.de

[lina]

$ 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

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.

>
> Kind regards

Best regards,

[Andreas Tille]

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