I am past the wx module. It was just as suggested, I had python2.4
first in line,
wxpython was made for python2.3 (what a dummy) and it could not find it.
Fixed here.
Now I am onto usrp stuff, trying to get the burn-basic-eeprom to run.
I got the following error message and follow on listings
On Mon, Apr 18, 2005 at 11:24:22AM -0400, Robert W McGwier wrote:
I am past the wx module. It was just as suggested, I had python2.4
first in line,
wxpython was made for python2.3 (what a dummy) and it could not find it.
Fixed here.
Now I am onto usrp stuff, trying to get the
Similar situation down here in Brazil, but
after adding the softlink it complains with
file not found... or something similar...
Any tips on where to put some break code to help debug
the issue?
Rgrds,
Angilberto.
--- [EMAIL PROTECTED] wrote:
I fixed it by adding the following softlink:
ln
Fails at work on my SUSE 9.2 install and succeeds at home on my SUSE 9.2
install.
Running python 2.3.4 at home and Python 2.4.1 at work. However, I just
installed
2.4.1 at work. I got the same error messages before today with 2.3
first in the path.
Having 2.4.1 first seems not to have helped
In my limited experience with this stuff, DO NOT install multiple
versions of wxPython. Just have 2.5.
-Ilia
On Fri, 2005-04-15 at 14:33 -0500, LRK wrote:
Probably a clue here somewhere.
'import wx' fails but 'import wxversion' works
Then I can select the version and get a different
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,
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
I fixed it by adding the following softlink:
ln -s ./wx-2.5.5-gtk2-ansi/wx
in the .../lib/python2.3/site-packages
directory.
Worked fine after that. There is a wx.pth in the site-packages directory
that Python should use to follow it, but it doesn't work. This was a
quick fix.
Hope that
On Thu, Apr 14, 2005 at 03:04:09PM -0500, LRK wrote:
On Thu, Apr 14, 2005 at 12:01:11PM -0500, Suvda Myagmar wrote:
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.
Did you export PYTHONPATH?
Where is
On Thu, Apr 14, 2005 at 01:23:08PM -0700, John Clark wrote:
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
Eric Blossom wrote:
On Thu, Apr 14, 2005 at 01:23:08PM -0700, John Clark wrote:
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
On Thu, Apr 14, 2005 at 03:09:47PM -0700, Eric Blossom wrote:
On Thu, Apr 14, 2005 at 03:04:09PM -0500, LRK wrote:
On Thu, Apr 14, 2005 at 12:01:11PM -0500, Suvda Myagmar wrote:
Setting PYTHONPATH to /home/myagmar/gr/lib/python2.3/site-packages
is supposed to fix that. Doesn't for me
On Fri, Apr 15, 2005 at 12:07:34AM -0500, LRK wrote:
On Thu, Apr 14, 2005 at 09:52:33PM -0700, Eric Blossom wrote:
gr% python
Python 2.4.1 (#2, Apr 12 2005, 10:46:06)
[GCC 3.4.2 [FreeBSD] 20040728] on freebsd5
Type help, copyright, credits or license for more information.
import sys
Eric Blossom wrote:
The lowest version of wxPython that we support is 2.5.2.7
wx is the main wxPython module in 2.5
See http://www.wxpython.org for latest binaries.
Eric
Note that you will probably get /very/ confusing error messages if you
end up with more then one version of wxPython installed.
14 matches
Mail list logo
