On Fri, Nov 24, 2006 at 01:42:41AM -0800, Andi Vajda wrote: > Would you like to contribute a configure script ?
I don't know how to write one. I also don't know how to install PyLucene, so therefore I don't know how to tell a script to do it. > All exceptions are listed in PyLucene's README [3]. Again, if something > in the PyLucene documentation is wrong or misleading, contributions, > corrections and patches are welcome. The real problem is not that the README file has any mistakes in it, but rather that it is haphazard documentation. It just didn't connect the dots for me. You can only expect so much from documentation recycled from a conference presentation and stashed in a file called README. If PyLucene had a wiki, that would give it a better chance to evolve into good documentation. But since you mention it, the README file has not been adapted to Lucene 2.0. > The "Lucene in Action" book [4] is also a great source of documentation and > samples for using Lucene. It's a pretty good book, when the authors are not too busy singing praises to Doug Cutting and Lucene. I don't even disagree with these praises, but they get in the way. > Almost all samples from this book were ported to > python and PyLucene [5]. Since you mention it, LuceneBenchmark.py is not adapted to Lucene 2.0. > Maybe someone among the 90% of people not yet using PyLucene is going to step > forward and make some contribution improving on documentation, installation > or otherwise ? Of course, you can only expect people to start using it first, and then contribute. -- /\ Greg Kuperberg (UC Davis) / \ Home page: http://www.math.ucdavis.edu/~greg/ \ / Visit the Math ArXiv Front at http://front.math.ucdavis.edu/ \/ * All the math that's fit to e-print * _______________________________________________ pylucene-dev mailing list [email protected] http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
