ok, sorry for the long wait.
I tried this on both my work (XP) and home PC (Vista64) and they are
both consistent.
I had both Python2.6 and Python 3.0 installed.
wxPython didn't like that.
As soon as I uninstalled Python3.0, my wxPython started running again.
Must be some kind of registry thing.
jefm wrote:
I ran the script from a command line, so it is not a file association
thing.
Ummm... if you ran it by just typing the script name --
c:\test\whatever.py rather than c:\pythonxx\python c:\test\whatever.py --
then it certainly could be a file association issue.
I do have multiple ve
I ran the script from a command line, so it is not a file association
thing.
I do have multiple versions of Python installed on that machine. I
will uninstall them all and install a single version from clean.
Thanks for the suggestion
--
http://mail.python.org/mailman/listinfo/python-list
jefm wrote:
when I call "import wx" from the interactive console, it works (i.e.
it doesn't complain).
But when I call the same from a script, it complains that it can not
find the wx module.
works for interactive
Python 2.6.1 (r261:67517, Dec 4 2008, 16:
when I call "import wx" from the interactive console, it works (i.e.
it doesn't complain).
But when I call the same from a script, it complains that it can not
find the wx module.
works for interactive
Python 2.6.1 (r261:67517, Dec 4 2008, 16:51:00) [MSC v.