I've uploaded Xapian 1.0.11 (including Search::Xapian 1.0.11.0), which
as usual you can download from:
http://xapian.org/download
Starting from this release, I'm going to include SHA1 checksums of
the released files in the release announcement. For 1.0.11 these are:
480fd99617975c1aaf9127cd7c7166bc05d07eb1 Search-Xapian-1.0.11.0.tar.gz
217c7fb1754d0aeaf82c3ab83d5ec0881099bb61 xapian-bindings-1.0.11.tar.gz
e2ebc5df461a28eca9903de40d9c2f18cd592050 xapian-core-1.0.11.tar.gz
bd4b21751b627977a430a56b5947568ae23264e3 xapian-omega-1.0.11.tar.gz
I had hoped to also start to GPG sign release announcements, but the
mailing list seems to block PGP/MIME currently and James is the list
admin and away at the moment. I'll resend the checksums signed once
we sort that out. Expect to see GPG signed release announcements in the
future.
This release fixes a number of bugs and improves efficiency in a few
cases.
Notable changes in this release:
* Enquire::get_mset() now throws UnimplementedError if there's a
percentage cutoff and sorting is primarily by value - this has never
been correctly supported and overall it seems better to warn people
than give incorrect results. However, this change means that existing
applications will now fail visibly in some cases when they might have
seemed to be working (but were actually returning wrong results).
* Enquire::set_sort_by_value() (and similar methods) had an optional
"ascending" parameter which defaulted to true. However, the
interpretation of "ascending" was counter-intuitive: ascending=true
would result in the reverse of the natural ordering. To deal with
this while maintaining API and ABI compatibility in 1.0.x, we've
renamed the parameter to "reverse" but kept its interpretation and
default the same. In 1.1.0, we're going to deprecate the default
value, so you'll need to start specifying "true" explicitly. We
suggest you make this change sooner as it's API compatible for all 1.0
releases too.
* The child process used to implement WritableDatabase locking in flint
now changes directory to "/" so that it doesn't block unmounting
of any
partitions and closes any open file descriptors which aren't relating
to locking so that if those files are closed by our parent and deleted
the disk space gets released right away.
* We now keep Python references to Sorter, Stopper, and
ValueRangeProcessor objects which get set on other objects to avoid
segmentation faults if they go out of scope before the object they are
set on does.
* Omindex now supports indexing Microsoft Office 2007 formats and XPS files.
For a more detailed overview see:
http://trac.xapian.org/wiki/ReleaseOverview/1.0.11
The full lists of user-visible changes are linked to from there, and are
also available via the "[news]" links on the download page.
As always, if you encounter problems, please report them here, or to
the bugtracker: http://xapian.org/bugs
Cheers,
Olly