Release Notes for 1.0.0

Please don't "report" new problems by adding them here as they may not be noticed. Instead use the bug tracker or mailing lists to report problems. You'll certainly get a much quicker response that way.

xapian-core

• The NumberValueRangeProcessor class isn't very well thought out, and is only useful for numbers the same length. Avoid using it for now.

omega

• There's a small (and long-standing - this dates back to at least Omega 0.8.2) issue in the HTML parser to do with handling tags with only whitespace between them. (​patch)
• Query parsing errors aren't being handled correctly, due to the code not being updated in line with changes in how query parser errors are reported in 1.0.0. (​patch)

xapian-bindings

• Tcl's package require command doesn't allow differing major version numbers (even if -exact isn't specified). You'll need to update your own Tcl scripts to say package require xapian 1.0.0 if you specify a minimum version after package require xapian. This issue also means that make check fails for the Tcl bindings (​patch), and that the Tcl example scripts don't work (​patch1 ​patch2).

• The Query constructor used to make ValueRange queries got missed out of the bindings. [Resolved in HEAD]

• We suspect that the Python bindings will not work in conjunction with Python 2.3 and Apache's mod_python module (the result will be a deadlock when the first Xapian object is instantiated). It is also possible that this applies to later versions of Python. We'll update this comment as we determine more information.

• "make check" doesn't pass with Python 2.2. This is because the compatibility layer for accessing the sequence API doesn't work due to limitations in Python 2.2's slice support. For now, we recommend using a more recent Python version, or updating applications not to use the (deprecated) compatibility layer. This will be a necessary update in any case when xapian 1.1.0 is eventually released.