Hi Andi, How come you decided to move away from SWIG? I was under the impression that SWIG makes it easy to keep a port in sync with the original and doesn't require "manual rewrites" in another language.
Otis ----- Original Message ---- From: Andi Vajda <[EMAIL PROTECTED]> To: [email protected] Sent: Wednesday, March 29, 2006 3:57:44 PM Subject: [pylucene-dev] PyLucene no longer uses SWIG As of release 2.0, on the PyLucene development trunk, SWIG is no longer used. Instead, the Python object wrappers are implemented by hand using the Python C type system. I uploaded a new PyLucene 2.0rc1-1 source tarball to: http://downloads.osafoundation.org/PyLucene/src/PyLucene-src-2.0rc1-1.tar.gz The handwritten wrappers represent about 20,000 lines of C++ code, a lot of boilerplate. Although macros are heavily used, the rather repetitive nature of this code makes it easy to make copy/paste mistakes along the way. All PyLucene unit tests and samples are passing but I expect typos and mistakes to still be lurking. If you find something wrong, it'll most likely crash or report an InvalidArgsError that should be trivial to fix by following the general argument passing patterns used with parseArg() and parseArgs(). Please report these bugs and/or submit patches to fix them. I also removed a number of Java Lucene deprecated methods as this is the main purpose of the upcoming Java Lucene 2.0 release. I had to fix many unit tests and samples along the way. Most of the changes had to do with using the new Field() creation APIs and the new BooleanQuery clause adding APIs. Andi.. _______________________________________________ pylucene-dev mailing list [email protected] http://lists.osafoundation.org/mailman/listinfo/pylucene-dev _______________________________________________ pylucene-dev mailing list [email protected] http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
