So I change "import digital_swig" to "from gnuradio.digital import digital_swig" and the complaining disappeared. Seems for these python modules, i still need to give a full path, even I have imported the gnuradio, gnuradio.digital in the beginning of the code.
--
Alex,
On Tue, Nov 29, 2011 at 9:57 AM, Tom Rondeau <trondeau1122@gmail.com> wrote:
On Tue, Nov 29, 2011 at 1:40 AM, Alex Zhang <cingular.alex@gmail.com> wrote:
I am using the this example to test the installed next branch of josh:
http://gnuradio.org/cgit/jblum.git/tree/gr-digital/python/pkt2.py?h=next
How ever, the digital_swig is not recognized. And I also checked the changeset at http://gnuradio.org/redmine/projects/gnuradio/wiki/ChangeSetsNothing related is found.Traceback (most recent call last): File "./pkt2.py", line 23, in <module> import digital_swig ImportError: No module named digital_swigCan someone tell me where to find this package now?--
Alex,Dreams can come true – just believe.It looks like you have some left-over code laying around. The pkt2.py is gone and we use pkt.py now, instead. Something must have gotten left behind with a checkout or merge at some point.As for the digital_swig, that's the "real" name of the SWIG'd-up gr-digital module that we export into digital. The internal gr-digital python modules use digital_swig, though.Make sure you've cleaned up previous installs, to a git clean -dxf in your gnuradio checkout and reinstall. Hopefully that'll fix your problems.Tom
Alex,
Dreams can come true – just believe.
No comments:
Post a Comment