userharbor-inmemory is a minimal, contract-tested UserStore implementation for UserHarbor. It can be installed directly for tests and examples or used as a GitHub template when building a custom storage integration.
Installation
pip install userharbor-inmemory
The package depends on userharbor and has no database or framework dependencies.
Usage
from userharbor import UserHarbor
from userharbor_inmemory import InMemoryUserStore
store = InMemoryUserStore()
harbor = UserHarbor(
secret_key="your-secret-key",
store=store,
email_sender=email_sender,
)
Each InMemoryUserStore instance starts empty and keeps its data for the lifetime of that instance.
The store implements the complete UserHarbor persistence contract:
- users and password hashes
- case-insensitive username lookup and uniqueness with original casing preserved
- email verification and password reset tokens
- sessions and session refresh
- roles and permissions
- user-role and role-permission assignments
- commit, rollback, and nested transaction behavior
Each user has at most one active email verification token and one active password reset token. Storing a replacement invalidates the previous token. Users may have multiple active sessions.
Use as an integration template
Select Use this template on GitHub and create a new repository. The generated repository starts with a complete implementation and a passing contract suite, so backend code can be replaced incrementally while the tests continue to verify UserStore behavior.
GitHub copies files without replacing project-specific names. After creating a repository:
- Rename the distribution in
pyproject.toml. - Rename the
userharbor_inmemorypackage andInMemoryUserStoreclass. - Update project metadata, links, badges, and this README.
- Replace the in-memory dictionaries and snapshot transaction with the target backend.
- Adapt the
user_storefixture intests/conftest.pyto create and clean up the backend. - Keep backend-specific tests separate from the shared contract suite.
- Run the complete test suite before publishing.
The contract tests stay intentionally small in this repository:
# tests/test_user_store_contract.py
from userharbor.testing.user_store_contract import * # noqa: F403
# tests/conftest.py
import pytest
from userharbor_inmemory import InMemoryUserStore
@pytest.fixture
def user_store() -> InMemoryUserStore:
return InMemoryUserStore()
See the UserStore contract testing guide and custom integrations guide for the complete behavioral requirements.
Development
Install the project and run its tests:
uv sync
uv run pytest
The suite imports the shared contract distributed with UserHarbor. Tests specific to this package remain in tests/test_public_api.py.
To develop against an unpublished local UserHarbor checkout, keep both repositories in the same parent directory and run:
uv run --with-editable ../userharbor pytest
Limitations
InMemoryUserStore is deliberately small. It does not provide persistence across process restarts, cross-process sharing, durable transactions, or concurrency guarantees. Its snapshot-based transaction implementation exists to reproduce the atomic behavior required by UserHarbor in tests and examples.
License
UserHarbor In-Memory is licensed under the MIT License. See LICENSE for details.
Metadata
Release files for userharbor-inmemory 0.4.0
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 | Actions |
|---|---|---|---|---|
| userharbor_inmemory-0.4.0.tar.gz | 5.3 kB | Without provenance | Details for userharbor_inmemory-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| userharbor_inmemory-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for userharbor_inmemory-0.4.0-py3-none-any.whl |
Total release size: 11.1 kB
Release files / userharbor_inmemory-0.4.0.tar.gz
| Download URL | userharbor_inmemory-0.4.0.tar.gz |
|---|---|
| Size | 5.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
459fbf1810e52617f8182b159d115dff843cbc980b8ff423c8be033974287a6c
|
|
BLAKE2b-256 checksum How to use checksums |
b2527e23782375db5d94824aa14453c6d10f98f4c4fb2a4e43d115b0fec97794
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.6 {"installer":{"name":"uv","version":"0.13.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"22.04","id":"jammy","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / userharbor_inmemory-0.4.0-py3-none-any.whl
| Download URL | userharbor_inmemory-0.4.0-py3-none-any.whl |
|---|---|
| Size | 5.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6f107d3bc1fc7e2c7fcf98714851c96f5e7591935b2ea642be8855a1f9f85ab1
|
|
BLAKE2b-256 checksum How to use checksums |
e48301f5d8f21d1cb6257b721bb7e25ef6f349d52feb9534950a3c343a40ad56
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.6 {"installer":{"name":"uv","version":"0.13.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"22.04","id":"jammy","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for userharbor-inmemory 0.4.0
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.