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 burn-ba
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 th
On Fri, Apr 15, 2005 at 01:44:52PM -0700, Eric Blossom wrote:
> On Fri, Apr 15, 2005 at 02:33:38PM -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 error:
> >
>
> OK. D
On Fri, Apr 15, 2005 at 02:33:38PM -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 error:
>
OK. Does the version of python that the wxPython binary was built
against match the ver
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 differ
Probably a clue here somewhere.
'import wx' fails but 'import wxversion' works
Then I can select the version and get a different error:
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 i
