Skip to main content

praxicraft-shared

Stateless Python utilities shared by Praxicraft backends (Practice, auth, notifications, billing, support, Tutor, LLM clients). Products pin a PyPI version. No Django ORM, settings, or product business logic lives here.

PyPI https://pypi.org/project/praxicraft-shared/
Current version 0.9.0 (see pyproject.toml)
Python 3.11+

Contents

  1. About
  2. Install in a product
  3. Local development
  4. What’s in the package
  5. Release
  6. Docs and deeper integrations

About

Hard rules:

  1. Stateless — no Django models, ORM, Celery, or package-owned Redis singletons
  2. No django.conf.settings — callers inject URLs and keys
  3. No product logic (XP, Assess scoring, Tutor mastery)
  4. Semver via git tags + PyPI — breaking JWT/auth contracts = major bump

Planning history: Practice shared docs.


Install in a product

Published on PyPI:

pip install praxicraft-shared==0.9.0

Docker / CI need no GitHub token — public index only.

Local editable (sibling checkout):

pip install -e ~/Desktop/praxicraft-shared

Local development

cd ~/Desktop/praxicraft-shared
pip install -e ".[dev]"
ruff check src tests
pytest

What’s in the package

Module Role
jwt_utils Validate RS256 access JWTs (JWKS / PEM)
auth_client HTTP client for praxicraft-auth
org_client Auth organisation directory
billing_client Entitlements, checkout, cancel/resume
notifications_client Send, events, prefs, push, inbox
support_client Support tickets API
ai_service Thin client for praxicraft-llm (chat, streaming, tools, get_speech_audio)
exec bureau-exec v1 and v2: get_languages, build_job, build_v1_job (SQL, Linux, platform cases, Python test harness), enqueue_job, await_result (sync and async), one ExecResult for both, summarize_tests scoring, the wire contract (exec.contract) and an in memory executor for tests (exec.testing)
s3_client Injectable MinIO/S3 helpers
service_token Parse product:token / JSON maps
error_envelope Standard success/error shapes
events Event envelope helpers
email/ Shared HTML/text email templates (rendered by notifications)
secret_crypto Fernet encrypt/decrypt (inject key)
work_email / hibp Email helpers / HIBP check

Release

  1. Bump version in pyproject.toml and __version__ in src/praxicraft_shared/__init__.py.
  2. Merge to main.
  3. Tag vX.Y.Z and push the tag (triggers Publish), or Actions → Publish → Run workflow with that existing tag.
  4. GitHub Actions publishes to PyPI via Trusted Publishing and creates a GitHub Release.

Pushing main alone runs CI only — it does not publish to PyPI until a v* tag exists.


Docs and deeper integrations

Link Topic
notifications PRODUCT-INTEGRATION How products call notifications_client
support PRODUCT-INTEGRATION How products call support_client
auth README Application registry + JWT
billing README Entitlements client
Tutor README End-to-end product wiring
praxicraft-llm Gateway tokens for ai_service

Metadata

Release files for praxicraft-shared 0.11.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for praxicraft-shared 0.11.0
File Size Uploaded Provenance Actions
praxicraft_shared-0.11.0.tar.gz 88.2 kB With provenance Details for praxicraft_shared-0.11.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for praxicraft-shared 0.11.0
File Interpreter ABI Platform Actions
praxicraft_shared-0.11.0-py3-none-any.whl Python 3 none any Details for praxicraft_shared-0.11.0-py3-none-any.whl

Total release size: 232.9 kB

Release files / praxicraft_shared-0.11.0.tar.gz

Download URL praxicraft_shared-0.11.0.tar.gz
Size 88.2 kB
Tags Source
SHA-256 checksum
How to use checksums
a568019ee3c2c6119d0ace545b4340c3239bba57aefc869045a6a07b7792d8a0
BLAKE2b-256 checksum
How to use checksums
6a824145ce9f0137aa426f848954814908e6808c6f498f0be5c9abf5335faba5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.

Transparency log

Release files / praxicraft_shared-0.11.0-py3-none-any.whl

Download URL praxicraft_shared-0.11.0-py3-none-any.whl
Size 144.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4d55d8eab0748273c9942c525c6cde40fc0cb1d4d0ce2c05328e4a509164bae2
BLAKE2b-256 checksum
How to use checksums
666dd6fdd1058f7a4851fa81d2e431f6dc2314e690d259a8750dfc08a11e3086
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.

Transparency log

Security for praxicraft-shared 0.11.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.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for praxicraft_shared-0.11.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.

Transparency log

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page