MSW Binary installation

Hello there,
I want to run xrced, so downloaded wxpython binaries and installed it. (before this I installed python2.2). After installing wxPython, I tried to run xrced and it gave the error,
ImportError: No module named wxPython.wx

I am not able to get much from the readme.txt under the docs directory.

Any help regarding this is appreciated.

Thanks in advance,
Joseph

Hi all,

I've been trying to figure out how to go about deriving a class from
wxObject; I hit a big brick wall with wxObject.__init__(). It requires
two arguments for init, the second being a pointer. How does one go
about getting that pointer?

Or is it worth even bothering?

Joseph wrote:

Hello there, I want to run xrced, so downloaded wxpython binaries and
installed it. (before this I installed python2.2). After installing
wxPython, I tried to run xrced and it gave the error, ImportError: No
module named wxPython.wx

What directory is Python 2.2 installed in?

What directory did the wxPython installer suggest as a destination?

Did you use this directory or another?

If another, is that dir on your PYTHONPATH?

Did you use the Python 2.2 version of the wxPython installer?

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

Jeff Grimmett wrote:

Hi all,

I've been trying to figure out how to go about deriving a class from
wxObject; I hit a big brick wall with wxObject.__init__(). It requires
two arguments for init, the second being a pointer. How does one go
about getting that pointer?

You shouldn't need to derive from wxObject for anything in wxPython. It doesn't fully conform to the C++ wxObject and in wxPython is really just an implementaiton detail.

Or is it worth even bothering?

Probably not.

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

You shouldn't need to derive from wxObject for anything in
wxPython. It
doesn't fully conform to the C++ wxObject and in wxPython is
really just
an implementaiton detail.

I was working on that all-Python wxSocket* implementation we discussed a
while back, and wanted to be as true to the docs as possible. On
reflection, though, the best way is probably NOT to be 100% true to the
docs since this *is* a wxPython-only implementation.