In a bit of a rush, so no time to install wxPython 2.5 to test with it, but I just noticed a failure on AMD64 that looks like it may be a problem with the SWIG wrapper for wxSTC (this is with the stock "stable" wxpython and the "testing" wxpython-demo (both are version 2.4.2.4) packages on Gentoo):
mcfletch@raistlin:~$ python /usr/share/doc/wxPython-2.4.2.4/demo/demo.py
Traceback (most recent call last):
File "/usr/share/doc/wxPython-2.4.2.4/demo/Main.py", line 756, in OnClose
frame = wxPythonDemo(None, -1, "wxPython: (A Demonstration)")
File "/usr/share/doc/wxPython-2.4.2.4/demo/Main.py", line 443, in __init__
self.txt = DemoCodeViewer(self.nb, -1)
File "/usr/share/doc/wxPython-2.4.2.4/demo/Main.py", line 244, in __init__
PythonSTC.__init__(self, parent, ID)
File "/usr/share/doc/wxPython-2.4.2.4/demo/wxStyledTextCtrl_2.py", line 65, in __init__
self.SetMarginMask(2, wxSTC_MASK_FOLDERS)
File "/usr/lib/python2.3/site-packages/wxPython/stc_.py", line 285, in SetMarginMask
val = stc_c.wxStyledTextCtrl_SetMarginMask(self, *_args, **_kwargs)
OverflowError: signed integer is greater than maximum
Terminated
>>> from wx import stc
>>> stc.STC_MASK_FOLDERS
4261412864
which looks suspiciously like a 0xfe000000 that was intended to mean a negative value. (Oh, completely stops the demo from running on AMD64, btw).
Anyway, just wondering if this is all old news, or if I'll need to schedule some time to install 2.5 and track down these things for a proper bug report (it'll be a few weeks before I get that time, btw).
Have fun,
Mike
···
________________________________________________
Mike C. Fletcher
Designer, VR Plumber, Coder
http://www.vrplumber.com
http://blog.vrplumber.com