On Tue, 21 Mar 2006, Matthew O'Connor wrote:
Why are you removing SWIG from the picture? I haven't seen
anything come across my subversion feeds.
Because the code generated by SWIG is needlessly thick and slow. The 5,000
line PyLucene.i file translates into almost 60,000 lines of C++ and 2,000
lines of Python code. *None* of that generated Python code is actually needed.
All of that can be done in C++ directly, leaving out one layer of python calls
altogether.
For example, python -m timeit "from PyLucene import Object" "Object()"
runs in 12.4 usec per loop with the new code vs 33.2 usec with SWIG-generated
code.
Also, each and every release of SWIG breaks PyLucene and I've had to fix it
once too many.
I've become a lot more familiar with the Python C API over the past year
and SWIG's help is really no longer needed.
You haven't seen anything in subversion yet because I haven't checked in
anything so far. I spent a few days on this so far and have a few more to go.
Andi..
_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
