Josiah,
If you look at the wxpython-users mailing list I tracked down the problem to
WX not correctly capturing the python GIL. In our case, it was in
wxListBox.GetSelections but I saw the same in wxFileConfig
Michael,
I had brought up this particular problem with Robin Dunn before, and he
was adamant that wxPython was doing the right thing with the GIL.
Robin; seems that wxFileConfig and wxListBox.GetSelections are causing
the "GC object already tracked" exception; are you sure that those
classes are working properly?
- Josiah
···
"Michael Ihde" <mike.ihde@randomwalking.com> wrote:
On 4/7/06, Josiah Carlson <jcarlson@uci.edu> wrote:
>
>
> Josiah Carlson <jcarlson@uci.edu> wrote:
> > "Michael Ihde" <mike.ihde@randomwalking.com> wrote:
> > > I've received a similar bug at you reported (
> > >
> https://sourceforge.net/tracker/?func=detail&atid=109863&aid=795590&group_id=9863
> )
> > > way back in 2003. Did you ever find a solution to this problem?
> >
> > In my case, the problem I observed was caused by an interaction between
> > the compiler module and wx.FileConfig (even though they weren't sharing
> > any data structures). One or the other is doing crazy things that is
> > crashing Python.
> >
> > I ended up writing a slimmed down work-alike for wx.FileConfig in pure
> > Python, and I haven't noticed any crashes since.
>
>
> Well, I should say that the earlier problem didn't have issues with the
> compiler module (because I wasn't using it)... basically in my
> experience, wx.FileConfig has some issues somewhere, get rid of it if
> you are using it, and things should work again.
>
> - Josiah
>
>