Installation and customization
==============================

.. currentmodule:: apsw

.. _pypi:

PyPI (recommended)
------------------

APSW is on PyPI at https://pypi.org/project/apsw/

It can be installed in the same way as other packages::

    python3 -m pip install apsw

When you install from PyPI:

* The corresponding SQLite version is embedded privately inside
  and not affected by or visible to the rest of the machine or
  even the rest of the process.

  This means other modules and libraries will continue using
  whatever SQLite they would have before.  For example `Core Data
  <https://developer.apple.com/documentation/coredata>`__ on MacOS
  uses SQLite, but will not know of or be affected by the SQLite
  inside APSW.

* All :doc:`extensions <extensions>` are enabled, except ICU.

* :doc:`extra` are available

* `SQLITE_ENABLE_COLUMN_METADATA <https://www.sqlite.org/compile.html#enable_column_metadata>`__
  is enabled, providing :attr:`Cursor.description_full`

The PyPI releases include pre-built binaries for common platforms.  If yours is not covered, then
pip will download the source release and automatically compile with the same settings.  It will
require a C compiler and the Python development header files.

Encryption
^^^^^^^^^^

APSW compiled against SQLite with `SQLite3MultipleCiphers
<https://utelle.github.io/SQLite3MultipleCiphers/>`__ is available via
its author at https://pypi.org/project/apsw-sqlite3mc/

Linux/BSD provided
------------------

Most Linux & BSD distributions have packaged APSW which may trail the
SQLite and APSW releases by a year, or more. The distribution provided
APSW uses the system wide SQLite library.

.. list-table::
    :widths: auto

    * - Debian
      - Install `python3-apsw <https://packages.debian.org/python3-apsw>`__
    * - Fedora
      - Install `python3-apsw <https://packages.fedoraproject.org/pkgs/python-apsw/>`__
    * - Ubuntu
      - Install `python3-apsw <https://packages.ubuntu.com/search?suite=all&searchon=names&keywords=apsw>`__
    * - Gentoo
      - Install `dev-python/apsw <https://packages.gentoo.org/package/dev-python/apsw>`_
    * - Arch
      - Install `python-apsw <https://www.archlinux.org/packages/?q=apsw>`__
    * - FreeBSD
      - `databases/py-apsw <https://cgit.freebsd.org/ports/tree/databases/py-apsw>`__ in `Ports <https://docs.freebsd.org/en/books/handbook/ports/>`__

There is a `full list (150+)
<https://repology.org/project/python:apsw/versions>`__ of
distributions, the package name for APSW, and what APSW version they
are currently on.

.. _sources:

Source
------

It is recommended you get the source from `Github releases
<https://github.com/rogerbinns/apsw/releases>`__.  If you get the
source from `PyPi <https://pypi.org/project/apsw/>`__ then ensure you
edit the :file:`setup.apsw` file inside.

.. downloads-begin

* `apsw-3.53.0.0.zip
  <https://github.com/rogerbinns/apsw/releases/download/3.53.0.0/apsw-3.53.0.0.zip>`__
  (Source as zip, includes this HTML Help)

* `apsw-3.53.0.0.tar.gz
  <https://github.com/rogerbinns/apsw/releases/download/3.53.0.0/apsw-3.53.0.0.tar.gz>`__
  (Source as tar.gz, includes this HTML Help)

* `apsw-3.53.0.0.zip.cosign-bundle
  <https://github.com/rogerbinns/apsw/releases/download/3.53.0.0/apsw-3.53.0.0.zip.cosign-bundle>`__
  cosign signature for zip source

* `apsw-3.53.0.0.tar.gz.cosign-bundle
  <https://github.com/rogerbinns/apsw/releases/download/3.53.0.0/apsw-3.53.0.0.tar.gz.cosign-bundle>`__
  cosign signature for tar.gz source

.. downloads-end


.. _verifydownload:

Verifying your download
^^^^^^^^^^^^^^^^^^^^^^^

Github `source releases <https://github.com/rogerbinns/apsw/releases>`__ are
digitally signed so you can verify they have not been tampered with,
and were produced by the project maintainer.

`Sigstore <https://www.sigstore.dev/>`__ is used.  Instructions are
shown for the standalone  `cosign tool
<https://github.com/sigstore/cosign/releases>`__ (easiest,
recommended), and the `Python sigstore module
<https://pypi.org/project/sigstore/>`__.

Verify

  Checking the signature needs to provide the source release, the
  cosign bundle, the maintainer id, and issuer.  The command is all
  one line shown here across multiple lines for clarity, along with
  the expected successful output.

  .. verify-begin

  .. code-block:: console

    $ cosign verify-blob apsw-3.53.0.0.zip                        \
        --new-bundle-format                                       \
        --bundle apsw-3.53.0.0.zip.cosign-bundle                  \
        --certificate-identity=rogerb@rogerbinns.com              \
        --certificate-oidc-issuer=https://github.com/login/oauth
    Verified OK

    $ python3 -m sigstore verify identity apsw-3.53.0.0.zip       \
        --bundle apsw-3.53.0.0.zip.cosign-bundle                  \
        --cert-identity=rogerb@rogerbinns.com                     \
        --cert-oidc-issuer=https://github.com/login/oauth
    OK: apsw-3.53.0.0.zip

  .. verify-end

  Check for a success exit code, and verified message.

.. _build:

Building and customization
--------------------------

APSW is configured for standard building (:pep:`518`)

.. code-block:: console

    $ python3 -m build

You will need to update the MANIFEST first if you are providing your
own SQLite, or if you are providing a ``setup.apsw`` with custom
configuration. `setuptools
<https://setuptools.pypa.io/en/latest/index.html>`__ is used to
compile the extension.  You can use it directly instead by invoking
``setup.py``.

Build process
^^^^^^^^^^^^^

A series of commands and options are given to :file:`setup.py` in this pattern:

.. code-block:: shell

    python setup.py cmdone --option --option value cmdtwo --option \
       cmdthree --option --option value

The only necessary command is **build**.  You can get help by `--help`:

.. code-block:: shell

    python setup.py build --help

Each command takes options which can be specified on the command line,
or in a configuration file named :file:`setup.cfg` or
:file:`setup.apsw`.  The leading double dash on options is omitted,
and dashes inside should become underscores.

.. literalinclude:: ../tools/setup-pypi.cfg
   :language: ini

SQLite options
^^^^^^^^^^^^^^

It is important to understand `SQLite's compile time options
<https://www.sqlite.org/compile.html>`__.  They provide control
over functionality and APIs included or excluded from SQLite.

APSW needs to know the options chosen so it can adapt.  For example if
extension loading is omitted from SQLite then APSW also needs to omit
the same functionality, otherwise compilation or linking will fail.

Finding SQLite
^^^^^^^^^^^^^^

APSW can fetch SQLite as detailed below, and places it in a
:file:`sqlite3/` subdirectory.  You can place your own SQLite in that
directory.  If there is a :file:`sqlite3.c` (ie the `amalgamation
<https://www.sqlite.org/amalgamation.html>`__) then it will be
statically included inside APSW.  A compiled SQLite will be picked up
if present.  If none of that is present, then the standard compiler
locations are used (eg :file:`/usr/include` on Unix).

If :file:`sqlite3/sqlite3config.h` is present it is included before
:file:`sqlite3/sqlite3.c`.  It is a good location to put `platform
configuration
<https://www.sqlite.org/compile.html#_platform_configuration>`__ which
APSW's fetch does automatically by running :file:`configure`.


.. _setup_py_flags:

setup.py commands and their options
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

These are the relevant :file:`setup.py` commands and their relevant options.

.. _setup_build_flags:

build
#####

Does the complete build.  This will invoke `build_ext` - use only one of
`build` or `build_ext`.

.. list-table::
    :widths: auto

    * - ``--fetch``
      - Fetches the corresponding SQLite version amalgamation and all source
        to make :doc:`extra` available
    * - ``--enable-all-extensions``
      - Enables all the :doc:`standard extensions <extensions>`
    * - ``--enable``
      - A comma separated list of `options to enable that are normally
        off
        <https://www.sqlite.org/compile.html#_options_to_enable_features_normally_turned_off>`__
        omitting the :code:`SQLITE_ENABLE` prefix.  They will be
        uppercased.  eg :code:`--enable column_metadata,fts5`
    * - ``--omit``
      - A comma separated list of `options to omit that are normally
        enabled <https://www.sqlite.org/compile.html#_options_to_omit_features>`__
        omitting the :code:`SQLITE_OMIT` prefix.  They will be
        uppercased.  eg :code:`--omit automatic_index`


.. _fetch_checksums:

fetch
#####

This provides more fine grained control over what is fetched.

..  list-table::
    :widths: auto

    * - ``--version``
      - Specify an explicit version of SQLite to fetch
    * - ``--fetch-sqlite``
      - Downloads the SQLite amalgamation
    * - ``--all``
      - Downloads all SQLite source which makes the :doc:`extra`
        available
    * - ``--missing-checksum-ok``
      - APSW includes checksums of SQLite releases and will fail a
        fetch if you specify a version for which no checksum is known.
        This allows proceeding.


.. _matching_sqlite_options:

build_ext
#########

This performs the compilation of the C code, and provides more control than build.

..  list-table::
    :widths: auto

    * - ``--use-system-sqlite-config``
      - Uses :mod:`ctypes` to determine the system wide SQLite library
        compilation options
    * - ``--definevalues``
      - Additional #defines separated by commas.  eg :code:`--definevalues
        SQLITE_MAX_ATTACHED=37,SQLITE_EXTRA_INIT=mycore_init`
    * - ``--enable-all-extensions``
      - Enables all the :doc:`standard extensions <extensions>`
    * - ``--enable``
      - A comma separated list of `options to enable that are normally
        off
        <https://www.sqlite.org/compile.html#_options_to_enable_features_normally_turned_off>`__
        omitting the :code:`SQLITE_ENABLE` prefix.  They will be
        uppercased.  eg :code:`--enable column_metadata,fts5`
    * - ``--omit``
      - A comma separated list of `options to omit that are normally
        enabled <https://www.sqlite.org/compile.html#_options_to_omit_features>`__
        omitting the :code:`SQLITE_OMIT` prefix.  They will be
        uppercased.  eg :code:`--omit automatic_index`
    * - ``--apsw-no-old-names``
      - Excludes old non :pep:`8` :ref:`complaint name aliases
        <renaming>` from the extension and type stubs.

.. _pyodide:

Pyodide (WASM)
--------------

`Pyodide <https://pyodide.org/en/stable/index.html>`__ is a web
assembly Python distribution that can run in the browser or via NPM.
PyPI does not support pyodide binary packages yet, but you can compile
your own on a Linux host.

You should first download the source distribution listed at the top of
https://pypi.org/project/apsw/#files - the filename ends up being
``apsw-3.52.0.0.tar.gz`` in this example.  The `cibuildwheel
<https://cibuildwheel.pypa.io/>`__ tool is used for the building, and
is the same tool used for the PyPI builds of APSW.

.. code-block:: shell-session

  # Start out with a clean virtual environment
  $ python3 -m venv venv
  # Get cibuildwheel
  $ venv/bin/pip3 install cibuildwheel
  # Do the building which will download the necessary compiler and
  # Python parts
  $ venv/bin/cibuildwheel --platform pyodide apsw-3.52.0.0.tar.gz
  # When it has finished the result is in the wheelhouse directory
  $ ls wheelhouse/

You will then be able to install the wheel using `micropip
<https://micropip.pyodide.org/>`__.

.. code-block:: pycon

  >>> import micropip
  >>> await micropip.install("https://url/apsw-3.52.0.0-cp312-cp312-pyodide_2024_0_wasm32.whl")
  >>> import apsw

At this point you will be able to use APSW as normal.

.. _packagers:

Advice for packagers
--------------------

This is the recommendation for packagers such as Linux and BSD
distributions, who want APSW to use the system shared SQLite library.

* Use the source file from `github releases
  <https://github.com/rogerbinns/apsw/releases>`__.  Note you should
  use the zip or tar.gz file including the version number, not the github
  repository copy at the end.  The file is signed and :ref:`can be
  verified <verifydownload>`.

  The file also includes a copy of the built documentation in HTML
  format with no analytics in the ``doc/`` subdirectory.

* After extracting the zip or tar, replace the file named
  ``setup.apsw`` that sits alongside ``setup.py`` with the following
  contents:

  .. code-block:: ini

    [build_ext]
    use_system_sqlite_config = True

  This will probe the system SQLite shared library for its compilation
  options.  Various C level APIs are included or excluded from the shared
  library based on those options, so APSW needs to know at compilation
  time which APIs it can or can't call.

* You can compile APSW using whatever works for your packaging system.
  APSW complies with the latest `Python packaging guidelines
  <https://packaging.python.org/>`__ and metadata.  (The traditional
  `setuptools <https://github.com/pypa/setuptools>`__ is the build
  backend.) You will see lines like the following during build (note the
  ``Extracting configuration``).

  .. code-block:: console

    running build_ext
    Extracting configuration from libsqlite3.so.0
    SQLite: Using system sqlite include/libraries

* :source:`pyproject.toml` defines a script entry point (command line
  tool) for ``apsw`` which invokes the :doc:`shell`.  It is optional
  to package this.  A man page is included in the ``man/`` directory.

.. _testing:

Testing
-------

SQLite itself is `extensively tested
<https://sqlite.org/testing.html>`__. It has considerably more code
dedicated to testing than makes up the actual database functionality.

APSW includes tests which use the standard Python testing modules to
verify correct operation. New code is developed alongside the tests.
Reported issues also have test cases to ensure the issue doesn't
happen or doesn't happen again.  Use ``python3 -m apsw.tests`` to
run all the tests.  You can provide a ``-v`` option to see each test
as it is run.

Test output will look similar to this.

.. code-block:: output

  $ python3 -m apsw.tests
                  Python  /space/apsw/.venv-314/bin/python sys.version_info(major=3, minor=14, micro=0, releaselevel='final', serial=0) 64bit ELF
  Testing with APSW file  /space/apsw/apsw/__init__.cpython-314-x86_64-linux-gnu.so
            APSW version  3.51.2.0
      SQLite lib version  3.51.2
  SQLite headers version  3051002
      Using amalgamation  True
       SQLITE_SCM_BRANCH  branch-3.51
         SQLITE_SCM_TAGS  release version-3.51.2
     SQLITE_SCM_DATETIME  2026-01-09T17:27:48.405Z

  ...............................................................................................................................................................................................................................
  ----------------------------------------------------------------------
  Ran 223 tests in 46.654s

  OK


The tests also ensure that as much APSW code as possible is executed
including alternate paths through the code.  95.5% of the APSW code is
executed by the tests. In the source, there is a script that enables
extra code that deliberately induces extra conditions such as memory
allocation failures, SQLite returning error codes, Python APIs
erroring etc.  That brings coverage up to 99.6% of the code.

`Compiler sanitizers options
<https://en.wikipedia.org/wiki/AddressSanitizer>`__ are also used for
further validation.

To ensure compatibility with the various Python versions, a script
downloads and compiles all supported Python versions in both debug and
release configurations (and 32 and 64 bit) against the APSW and SQLite
supported versions running the tests.

In short both SQLite and APSW have a lot of testing!