scolta-python
AI-powered search with Pagefind — the Python language
binding of Scolta. A faithful port of scolta-php.
Scolta is a scoring/ranking/AI layer over Pagefind, a static client-side search
engine. The browser-side scoring engine (scolta-core compiled to WebAssembly)
re-ranks Pagefind results and drives an optional LLM tier (query expansion,
summarization, follow-ups). This binding does the server-side work:
- gets content out of the application,
- builds and maintains a Pagefind-compatible index in-process (pure-Python indexer — no Pagefind binary required at runtime), with an input-side token cache so re-indexing after a content edit only re-tokenizes changed pages,
- proxies AI calls (Anthropic native + any OpenAI-compatible endpoint),
- serves the reused WASM/JS/CSS asset bundle and exposes config.
The pure-Python indexer is the default (indexer: auto). The Pagefind
binary pipeline is ported too but is opt-in (indexer: binary), with the
same auto-fallback-to-Python-when-the-binary-is-unavailable behaviour as the PHP
binding.
Platform integration for Django/Wagtail lives in the companion scolta-django
package.
Status
Complete port of scolta-php, released as 1.0.x. See CLAUDE.md for the
porting conventions.
Requirements
- Python 3.10+
- Optional:
PyICU(the[icu]extra) for higher-quality Unicode diacritic normalization in the tokenizer. Without it the tokenizer uses astrtr-style fallback, exactly asscolta-phpdoes withoutext-intl.
Development
uv venv --python 3.12
uv pip install -e ".[dev]"
uv run pytest
uv run ruff check
Metadata
Release files for scolta 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| scolta-1.0.1.tar.gz | 4.3 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| scolta-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.1 MB
Release files / scolta-1.0.1.tar.gz
| Download URL | scolta-1.0.1.tar.gz |
|---|---|
| Size | 4.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8c7b2b86f4cd839fd631e58e4c7552eb69c4597a7e9ceb3dbe19df7ba5342a6c
|
|
BLAKE2b-256 checksum How to use checksums |
04b85fafd384071ae2cf5bacebcad5ac7914192385f9be06c0d5268309cff73a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.26 {"installer":{"name":"uv","version":"0.9.26","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / scolta-1.0.1-py3-none-any.whl
| Download URL | scolta-1.0.1-py3-none-any.whl |
|---|---|
| Size | 769.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
01ac56896fcd51cf33bab2fe50487dff0c77df8bb11868a7f111da1bb7b7cb71
|
|
BLAKE2b-256 checksum How to use checksums |
c07751d8eeed668f5af86419efd9ebe3de66fcc092e3cfe3a0a20e0fd844bf51
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.26 {"installer":{"name":"uv","version":"0.9.26","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for scolta 1.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.