Apsw

=========

The APSW license has been updated to allow you (at your option) to use
any `OSI approved license
<https://opensource.org/licenses/alphabetical>`__.

The :ref:`speedtest` has been updated to (optionally) use unicode
characters and to (optionally) increase the sizes of data items.

Fixed error handling code to not record SQLite error strings in some
situations where it was not necessary. This results in the code
executing a little faster.

=========

APSW has migrated from Subversion to `Mercurial
<https://en.wikipedia.org/wiki/Mercurial>`_ for source code control.
Hosting remains at `Google Code <https://code.google.com/p/apsw/>`_

Updated a test due to VFS xUnlock errors now being ignored sometimes
by SQLite (cvstrac 3946).

The downloads page in the help didn't mention the Windows Python 3.1
installer.

Running the test suite is now integrated into :file:`setup.py` so you
can do the building and testing all in one go. Sample command line::

$ python setup.py install test

The test suite will now check the functionality of the FTS3, RTree and
ICU extensions if they were included. (The Windows binary distribution
includes FTS3 and RTree by default.)

Fixed :issue:`55` where FTS3 was unintentionally omitted from the
Windows binary distribution.

Various documentation updates.

=========

Windows binary distribution includes Python 3.1.

Trivial tweaks to keep MSVC happy.

=========

Fixed :issue:`50` where :meth:`Blob.read` was returning *None*
on end of file instead of the documented (and correct) empty
string/bytes.

Corrected spelling of option in :ref:`apswtrace <apswtrace>` and only
output CURSORFROM if SQL tracing is on.

===========

Updated test code because SQLite 3.6.15 returns a different error code
on trying to register a function with too many arguments (see
cvstrac 3875).

===========

Changed some internal symbol names so they won't clash with similar
new ones used by SQLite in the amalgamation.

Added :attr:`apsw.using_amalgamation` so you can tell if APSW was
compiled using the `SQLite amalgamation
<https://www.sqlite.org/amalgamation.html>`__. Using the
amalgamation means that SQLite shared libraries are not used and will
not affect your code.

Added a checksums file so that when :file:`setup.py` downloads SQLite,
we know it hasn't been tampered with. (The :ref:`--fetch-sqlite
<setup_py_flags>` argument can be used to automatically download
SQLite.)