[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] No module named wx

From: John Clark
Subject: Re: [Discuss-gnuradio] No module named wx
Date: Thu, 14 Apr 2005 13:23:08 -0700
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a6) Gecko/20050111

LRK wrote:

On Thu, Apr 14, 2005 at 12:01:11PM -0500, Suvda Myagmar wrote:
I also got USRP hardware recently and installed the latest baseline and gnuradio packages to test the HW. When I ran an example this is what I got:

$ ./usrp_oscope.py
Traceback (most recent call last):
 File "usrp_oscope.py", line 26, in ?
   from gnuradio.wxgui import stdgui, fftsink, scopesink
File "/home/myagmar/gr/lib/python2.3/site-packages/gnuradio/wxgui/stdgui.py", line 24, in ?
   import wx
ImportError: No module named wx

Another thing that might give a clue to my trouble is while building cvs gnuradio-core make check failed:

$ make check
ERROR: test_gru_import (__main__.test_head)
Traceback (most recent call last):
File "./qa_kludged_imports.py", line 39, in test_gru_import
  from gnuradio import gru
File "/home/myagmar/gnuradio/gnuradio-core/src/python/gnuradio/gru/__init__.py", line 37, in ?
  exec "from gnuradio.gruimpl.%s import *" % (f,)
File "<string>", line 1, in ?
File "/home/myagmar/gnuradio/gnuradio-core/src/python/gnuradio/gruimpl/freqz.py", line 57, in ?
  import Numeric
ImportError: No module named Numeric

Setting PYTHONPATH to /home/myagmar/gr/lib/python2.3/site-packages
is supposed to fix that. Doesn't for me either. Still working on why.

There should be another "site-packages" where python is installed, in my
case /usr/local/lib/python2.4/site-packages. Last resort is to put files Numeric.pth and wx.pth in that directory which contain the whole path to the packages.

I'll chime in on the 'easy to intuit' requirements to get any of gr-* up, especially the gr-wxgui. Unfortunately other projects press and I have not been able to get a working 'graphical' user environment up, when most of the antecedent 'packages' don't seem to just build, and when they do the install seems not to place things in the 'right' places for building or using the gr-*
codes sets.

When I have time, I'll continue on.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]