Greg,
Actually the patch is against the Sword library and not the python
bindings. The swig library which generates the bindings (for several
languages) has serious issues with nested classes and a recent change in
Sword linrary added a nested class that basically has broke the ability to
even make the bindings. The code attached basically makes the sword class
no longer nested. It should have no impact on anything other than to
de-nest the class. Their may be other nested classes; but in this specific
case because the nested class was reference from another class the generated
code was broken.Nathan. -----Original Message----- From: Greg Hellings [mailto:[email protected]] Sent: Monday, October 19, 2009 12:03 PM To: SWORD Developers' Collaboration Forum Subject: Re: [sword-devel] Submitting a Patch against 1.60svn You can send it to the mailing list. The Python bindings are maintained primarily by the BPBible team, from what I understand, so you can also get in touch with them for more help on the binding specifically. --Greg On Mon, Oct 19, 2009 at 11:52 AM, Nathan Anderson <[email protected]> wrote: > > Is their someone I can/should send a patch to that fixes the > python swig bindings issues in 1.6/1.6svn. Or do I send it to the mailing list? > > Nathan > > > _______________________________________________ > sword-devel mailing list: [email protected] > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > _______________________________________________ sword-devel mailing list: [email protected] http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
sword160-unnest.diff
Description: Binary data
_______________________________________________ sword-devel mailing list: [email protected] http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
