[Xapian-discuss] Omindex python - first version.

☼ 林永忠 ☼ (Yung-chung Lin) henearkrxern at gmail.com
Sun May 31 04:09:09 BST 2009


Hi all,

I'm also building a xapian-based indexer/searcher in perl.
The code is available here: http://code.google.com/p/perlax/
It's still in its infancy and has a lot to improve. Thanks.

Cheers,
Yung-chung Lin

On Fri, May 29, 2009 at 1:13 AM, Srijon Biswas <srijon.biswas at googlemail.com
> wrote:

> Hi all.
>
> I've put up another version of the python based indexer up at
> https://launchpad.net/xapian.python.indexer.
> The release is in trunk itself. I will use that as the place to check in
> any
> changes in the code.
>
> The name has been changed to xapian_python_indexer to avoid confusion with
> the omindex code. The code has been heavily changed. Unluckily due to the
> move to Launchpad from my regular repository where it was a part of my
> project, the changeset from last time has been lost. (If someone knows how
> to get that, I can try and get it out).
>
> Main changes:
> - testcases
> - bugfixes (lots, and major ones)
> - some optimizations
>
> You will need to install BeautifulSoup (
> http://www.crummy.com/software/BeautifulSoup/).
>
> To run the test cases, just call: "python test/test_xapian_py_indexer.py"
> To run the app itself: "python ./xapian_py_indexer.py"
> * The "./" is necessary right now - it's a bug that I'll fix by the next
> release.
>
> PS: I realize that making the release via this mailing list may not be what
> the list is intended for. This should be the last mail on the matter.
>
> Thanks,
> Srijon.
>
>
> On Wed, May 27, 2009 at 12:48 PM, Olly Betts <olly at survex.com> wrote:
>
> > On Wed, May 27, 2009 at 09:26:03AM +0100, Srijon Biswas wrote:
> > > On a related note, is there some test set/test data that can be used to
> > > validate the output? ie. is there some specific testing that can be
> done
> > to
> > > validate the omindex / scriptindex applications?
> >
> > I've been intending to put together such a testsuite for a while, but
> > have yet to actually do so.
> >
> > Mostly it needs a framework - then all new features would be expected to
> > have tests, and all bugs to have regression tests where feasible.
> > Existing stuff can be covered incrementally, probably guided by code
> > coverage reports from lcov (we have this set up for xapian-core as of a
> > few months ago and it has already shaken out a few bugs in obscure
> cases).
> >
> > Cheers,
> >     Olly
> >
>
>
>
> --
> ===============
> www.line-42.com
> ===============
> _______________________________________________
> Xapian-discuss mailing list
> Xapian-discuss at lists.xapian.org
> http://lists.xapian.org/mailman/listinfo/xapian-discuss
>


More information about the Xapian-discuss mailing list