Re: [sword-devel] Python bindings cause python crash

2007-12-20 Thread Jon Brisbin
This is probably why I get a crash when I exit my python shell after testing the Sword module from the command line. Now I'm trying to figure out how to best use modules. I think, for the time being, I'll use the same methodology that MacSword uses, which is to place the ".swd" modules insi

Re: [sword-devel] Python bindings cause python crash

2007-12-19 Thread Ben Morgan
Hi, Instead of: >>> from Sword import * >>> mf = MarkupFilterMgr(FMT_WEBIF) >>> mgr = SWMgr(mf) Try >>> from Sword import * >>> mf = MarkupFilterMgr(FMT_WEBIF) >>> mf.thisown = False >>> mgr = SWMgr(mf) mf.thisown = False tells swig not to GC the sword object. This may or may not help. I have

[sword-devel] Python bindings cause python crash

2007-12-19 Thread Jon Brisbin
I've got my _Sword.so module to compile and I statically linked libsword.a and libclucene.a into it. So far, I'm able to create the objects fine, but when I try to get my modules, Python crashes with the following trace: Process: Python [3639] Path:/System/Library/Framew