Python client for Basepair

Python bindings for Basepair's API and command line interface (CLI).

Sentry & custom metrics (optional)

Install with Sentry support:

pip install basepair[sentry]

The library provides shared Sentry init and entity metric constants so consumer apps (Pinda, webapp, ivfapp, kmap) do not duplicate scrubbing, sampling, or metric naming.

Important: basepair-python does not read environment variables for Sentry or metrics. Each app loads its own config and passes explicit parameters.

Sentry init

from basepair.sentry import init_sentry

init_sentry(
    dsn=os.environ.get("SENTRY_DSN"),
    environment=os.environ["MODE"],
    release=os.environ["VERSION"],
    service="pinda-backend",
    traces_sample_rate=float(os.environ["SENTRY_TRACES_SAMPLE_RATE"]),
    profile_sample_rate=float(os.environ["SENTRY_PROFILE_SAMPLE_RATE"]),
    project_name=os.environ.get("PROJECT_NAME"),
    customer_app=os.environ.get("CUSTOMER_APP"),
    debug=os.environ.get("SENTRY_DEBUG") == "true",
    low_value_transactions=("/api/health", "/api/health/"),
)

Empty dsn → no-op (safe for local dev).
Required when dsn is set: environment, release, service, traces_sample_rate, profile_sample_rate.
Optional: project_name, customer_app, debug, low_value_transactions, server_name, enable_logs, enable_metrics.
enable_logs / enable_metrics are passed through to sentry_sdk.init only when set. Omit them for SDK defaults (Sentry Logs off; custom metrics on).

Django apps can use request context helpers:

from basepair.sentry.django import SentryContextMiddleware, set_request_sentry_context

Entity metrics

basepair.metrics is a safe emit helper plus shared metric name constants. The HTTP client does not auto-emit — each app records metrics in its own PIs / workflows, into its own Sentry DSN.

Webapp — METRIC_ANALYSIS_* → webapp.entity.analysis.*
Pinda — METRIC_PINDA_ANALYSIS_* → pinda.analysis.* (use from all Pinda apps / Temporal workflows for consistent names)

from basepair.metrics import (
    METRIC_ANALYSIS_BULK_START,
    METRIC_PINDA_ANALYSIS_BULK_START,
    METRIC_PINDA_ANALYSIS_TERMINAL,
    Outcome,
    emit,
)

# Webapp DSN
emit.incr(METRIC_ANALYSIS_BULK_START, tags={"outcome": Outcome.SUCCESS})

# Pinda DSN (partiseq, revvity, …)
emit.incr(METRIC_PINDA_ANALYSIS_BULK_START, tags={"outcome": Outcome.SUCCESS})
emit.incr(METRIC_PINDA_ANALYSIS_TERMINAL, tags={"terminal_status": "completed"})

Requires sentry-sdk>=2.44.0 for the metrics API. No-op when Sentry is not initialized.

Spec: Confluence — Sentry Custom Metrics

Using MFA

Note: It is advisable to use MFA for increased security and best practices

After you have been added to the list of collaborators, you can verify if MFA has been activated for you by visiting collaboration page

How to build and push to pypi:

Automated publishing of distribution

In the testing stage of the changes, it is advisable to use Test PyPI. We already have github actions to publish on both Test PyPI and PyPI.

Manual way from local

python setup.py sdist bdist_wheel # This will create two files in a newly created dist directory, a source archive and a wheel:
twine upload dist/* # To upload it to Pypi
Uploading distributions to https://upload.pypi.org/legacy/
Enter your username:
Enter your password:

Note: username must be __token__ (not your pypi username) password is the token. You may generate the token -> token creation page.

That is it!

Below is a successful execution sample:

Uploading distributions to https://upload.pypi.org/legacy/
Enter your username: __token__
Enter your password:
Uploading basepair-2.0.7-py3-none-any.whl
100% ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 51.0/51.0 kB • 00:00 • 36.3 MB/s
Uploading basepair-2.0.7.tar.gz
100% ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 37.4/37.4 kB • 00:00 • 47.2 MB/s

View at:
https://pypi.org/project/basepair/2.0.7/

Metadata

Release files for basepair 3.5.4

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

Source distribution (sdist)

Source distribution for basepair 3.5.4
File	Size	Uploaded
basepair-3.5.4.tar.gz	83.7 kB	Sep 29, 2026	Details

Built distribution (wheel)

Table of built distributions (wheels) for basepair 3.5.4
File	Interpreter	ABI	Platform	Reset
basepair-3.5.4-py3-none-any.whl 115.0 kB Sep 29, 2026	Python 3	none	any	Details

Total release size: 198.7 kB

Release files / basepair-3.5.4.tar.gz

Download URL	basepair-3.5.4.tar.gz
Size	83.7 kB
Tags	Source
SHA-256 checksum How to use checksums	`c811fabb943bcb422adc6fe8320f955dc3d3ca801349d2034ac41007bf2b38e4`
BLAKE2b-256 checksum How to use checksums	`4df3f3979acd74e01ef8f04edde865603eb3553ca397c038b979ae81f7653631`
Upload date	Sep 29, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/7.0.0 CPython/3.14.7`

Release files / basepair-3.5.4-py3-none-any.whl

Download URL	basepair-3.5.4-py3-none-any.whl
Size	115.0 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`322c2bfd473b007412a7a16c856a7ae5ef4aaeee6ea3fb23919c6878de6d3bd8`
BLAKE2b-256 checksum How to use checksums	`089705503b2790eef5db9debd7bdc205c50c23d843ef9300ace502714defdf3a`
Upload date	Sep 29, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/7.0.0 CPython/3.14.7`