Franz Steinhaeusler wrote:
maybe you have 2.4.2 and I 2.4.
This looks like a wxPython problem, not a Python problem.
It might well be a version issue for you guys, but it's
more likely that a certain wxPython version is the culprit,
not a certain Python version.
Note however that the OP is
On Sun, 26 Feb 2006 10:35:13 -0600, Tim Chase
[EMAIL PROTECTED] wrote:
Trying to get my feet wet with wxPython (moving from just
command-line apps), I tried the obvious (or, at least to me
was obvious):
Start python, import wx and then do a help(wx) to see
what it can tell me.
I tried it on
Franz Steinhaeusler wrote:
On Sun, 26 Feb 2006 10:35:13 -0600, Tim Chase
[EMAIL PROTECTED] wrote:
Trying to get my feet wet with wxPython (moving from just
command-line apps), I tried the obvious (or, at least to me
was obvious):
Start python, import wx and then do a help(wx) to see
On 27 Feb 2006 04:55:15 -0800, André [EMAIL PROTECTED] wrote:
Franz Steinhaeusler wrote:
On Sun, 26 Feb 2006 10:35:13 -0600, Tim Chase
[EMAIL PROTECTED] wrote:
Trying to get my feet wet with wxPython (moving from just
command-line apps), I tried the obvious (or, at least to me
was
Trying to get my feet wet with wxPython (moving from just
command-line apps), I tried the obvious (or, at least to me
was obvious):
Start python, import wx and then do a help(wx) to see
what it can tell me.
Unfortunately, it spewed back a handful of errors, gasped,
wheezed and died
