Port setup.py to pyproject.toml

[simonw]

It's time.

[simonw]

Testing this manually:

uv run --with build python -m build

Gave me these:

sqlite-utils % ls -lah dist 
total 576
drwxr-xr-x   4 simon  staff   128B Nov 23 12:31 .
drwxr-xr-x@ 27 simon  staff   864B Nov 23 12:31 ..
-rw-r--r--   1 simon  staff    69K Nov 23 12:31 sqlite_utils-4.0a0-py3-none-any.whl
-rw-r--r--   1 simon  staff   214K Nov 23 12:31 sqlite_utils-4.0a0.tar.gz

Interesting that the wheel is so much smaller than the .tar.gz.

[simonw]

I had Codex investigate the size difference: https://gistpreview.github.io/?3c916a859f1d74f2f0f59034cd1b228c

Size Difference

• dist/sqlite_utils-4.0a0-py3-none-any.whl: 15 runtime files only (package modules + dist-info); 68,117 bytes compressed, 287,762 bytes
  uncompressed. Biggest files are sqlite_utils/db.py (156,869 bytes) and sqlite_utils/cli.py (90,603 bytes).
• dist/sqlite_utils-4.0a0.tar.gz: 77 files; 218,631 bytes compressed, 974,770 bytes uncompressed. It bundles docs and tests in addition
  to the package code.
• Extra bulk in the sdist comes from docs (docs/python-api.rst 104,600 bytes, docs/cli.rst 87,804, docs/changelog.rst 75,353, docs/cli-
  reference.rst 49,794) and tests (tests/test_cli.py 76,805, tests/test_create.py 46,101, etc.), plus sqlite_utils.egg-info metadata.
• The code files themselves are the same size in both archives; the larger size is due to shipping documentation and tests in the sdist,
  which is normal.

If you want the sdist smaller, we can update MANIFEST.in/build config to exclude docs/tests; otherwise the size gap is expected.

[simonw]

Turns out that's because my MANIFEST.in includes those deliberately!

sqlite-utils/MANIFEST.in

Lines 1 to 4 in 1587fec

	include LICENSE
	include README.md
	recursive-include docs *.rst
	recursive-include tests *.py

That's from this PR from 5 years ago:

• Explicitly include tests and docs in sdist #75

I've changed my mind, I'm going to NOT do that from here on.

[simonw]

... actually I'm going to keep with how this works already. I had not realized that SDIST is meant to include tests and docs, while whl is meant to be just what's needed to run the code. https://packaging.python.org/en/latest/discussions/package-formats/#what-is-a-source-distribution

[simonw]

Tested the wheel like this:

uv run --with ~/dev/sqlite-utils/dist/sqlite_utils-4.0a0-py3-none-any.whl python

>>> import sqlite_utils
>>> db = sqlite_utils.Database(memory=True)
>>> db
<Database <sqlite3.Connection object at 0x12cad5840>>
>>> def creatures():
...     yield "id", "name", "city"
...     yield 1, "Cleo", "San Francisco"
...     yield 2, "Lila", "Los Angeles"
... 
>>> db["creatures"].insert_all(creatures(), pk="id")
<Table creatures (id, name, city)>
>>> list(db["creatures"].rows)
[{'id': 1, 'name': 'Cleo', 'city': 'San Francisco'}, {'id': 2, 'name': 'Lila', 'city': 'Los Angeles'}]