[python-win32] activex controls gpf (win32all1.46, wxPython2.3.2.1, python2.2.1)

Mark Hammond mhammond@skippinet.com.au
Wed, 19 Jun 2002 11:57:18 +1000


> Anyway, here in-house we have been using some ActiveX controls (BeeGrid,
> Pro-Essentials) to interface with python code. Everything works fine with
> python 2.0, but now we are trying to upgrade to 2.2 so we can use the nice
> subclassing of native types, etc. The bug seems to be
> event-related -- i.e.
> after events are sent to/from the ax control, any further access becomes
> invalid, and leads to a GPF (specifically everytime in PyErr_Restore() (at
> the PY_XDECREF) in errors.c of the pythoncore code).

Unfortunately, I still haven't got around to making wxPython work here.
Look at the Pythonwin OCX demos, and see if you can get pythonwin to fail
using these controls.  If not, I am afraid I must assume it is in wxPython
:(

> Py2.2 and win32all1.42 (I believe). Robin Dunn, the maintainer of
> wxPython,
> in a reply to a sourceforge bug message, says he has problems
> with every new
> release of win32all, and has trouble debugging it :(.

I don't hear about them :(

> Anyhow, I've tried 1.42, 1.46, and 1.48 on this machine as well, but to no
> avail. The last version that seemed to work was with build 135, which I am
> now trying to see if it will compile for Py2.2, but I'm running into
> problems with SWIG (gives me a syntax error in pywintypes.i on
> line 56, but
> it looks harmless enough!). Is it even possible to run 135 with
> this version
> of Python, or are there "features" that will break? Just
> wondering about the
> feasibility of this plan.

I am afraid I am not really sure what you are asking here.  Using SWIG is
definately the long route and should be avoided in this case.

Mark.