Skip to main content

pysof - SQL on FHIR for Python

PyPI version Python versions License: MIT Downloads

High-performance FHIR data transformation for Python. Transform FHIR resources into tabular formats (CSV, JSON, Parquet) using declarative ViewDefinitions from the SQL on FHIR specification.

Built in Rust for speed, exposed to Python with a simple, Pythonic API. Part of the Helios FHIR Server project.

✨ Key Features

  • 🚀 High Performance: Native Rust implementation with minimal Python overhead
  • 📊 Multiple Output Formats: CSV, JSON, NDJSON, and Parquet
  • 🔄 Parallel Processing: Automatic multithreading with 5-7x speedup on multi-core systems
  • 📦 Streaming Support: Memory-efficient chunked processing for large NDJSON files
  • 🌐 Multi-Version FHIR: Supports R4, R4B, R5, and R6 (based on build features)
  • 🎯 Type-Safe: Leverages Rust's type safety with a Pythonic interface
  • ⚡ GIL-Friendly: the GIL is released during parsing and processing, so other Python threads stay responsive
  • 📨 Flexible Input: ViewDefinitions and Bundles as Python dicts or pre-serialized JSON (str/bytes)

🎯 Why pysof?

Working with FHIR data in Python just got faster. pysof lets you:

  • Transform complex FHIR resources into clean, analyzable tables without writing custom parsers
  • Process large datasets efficiently with automatic parallel processing and Rust-level performance
  • Use standard SQL on FHIR ViewDefinitions for portable, maintainable data transformations
  • Export to multiple formats (CSV, JSON, NDJSON, Parquet) for analytics, ML, or reporting workflows

Perfect for healthcare data engineers, researchers, and developers building FHIR-based analytics pipelines.

📥 Installation

pip install pysof

Supported Platforms:

  • Linux: x86_64 (glibc and musl)
  • Windows: x86_64 (MSVC)
  • macOS: AArch64 (Apple Silicon)
  • Python: 3.10, 3.11, 3.12, 3.13, 3.14

From GitHub Releases

Download pre-built wheels from the releases page:

pip install pysof-*.whl

🚀 Quick Start

Transform FHIR patient data to CSV in just a few lines:

import pysof

# Define what data to extract
view_definition = {
    "resourceType": "ViewDefinition",
    "id": "patient-demographics",
    "name": "PatientDemographics",
    "status": "active",
    "resource": "Patient",
    "select": [{
        "column": [
            {"name": "id", "path": "id"},
            {"name": "family_name", "path": "name.family"},
            {"name": "given_name", "path": "name.given.first()"},
            {"name": "gender", "path": "gender"},
            {"name": "birth_date", "path": "birthDate"}
        ]
    }]
}

# Sample FHIR Bundle
bundle = {
    "resourceType": "Bundle",
    "type": "collection",
    "entry": [{
        "resource": {
            "resourceType": "Patient",
            "id": "patient-1",
            "name": [{"family": "Doe", "given": ["John"]}],
            "gender": "male",
            "birthDate": "1990-01-01"
        }
    }]
}

# Transform to CSV
csv_output = pysof.run_view_definition(view_definition, bundle, "csv")
print(csv_output.decode('utf-8'))
# Output:
# id,family_name,given_name,gender,birth_date
# patient-1,Doe,John,male,1990-01-01

📖 Usage

Multiple Output Formats

import pysof
import json

# Transform to different formats
csv_result = pysof.run_view_definition(view_definition, bundle, "csv")
json_result = pysof.run_view_definition(view_definition, bundle, "json")
ndjson_result = pysof.run_view_definition(view_definition, bundle, "ndjson")
parquet_result = pysof.run_view_definition(view_definition, bundle, "parquet")

print("CSV Output:")
print(csv_result.decode('utf-8'))

print("\nJSON Output:")
data = json.loads(json_result.decode('utf-8'))
print(json.dumps(data, indent=2))

Advanced Options

import pysof

# Transform with pagination and filtering
result = pysof.run_view_definition_with_options(
    view_definition,
    bundle,
    "json",
    limit=10,                          # Limit results
    page=1,                            # Page number
    since="2023-01-01T00:00:00Z",     # Filter by modification date
    fhir_version="R4"                  # Specify FHIR version
)

Remote resolve() (Trusted Servers)

resolve() dereferences references against the input bundle by default. You can optionally let it fetch references that point at explicitly trusted FHIR servers and fold them into the resolution pool before rows are generated. This is off by default and gated by a strict allowlist (matching scheme + host + port

  • path-prefix; private/loopback addresses are blocked unless opted in).
import pysof

config = pysof.RemoteResolveConfig(
    ["https://fhir.example.org/r4"],   # trusted base URLs (allowlist)
    max_fetches=256,                    # per-run/-stream fetch cap
    max_depth=1,                        # chained-reference rounds
    allow_private_addresses=False,      # allow internal LBs (e.g. Traefik) by hostname
    bearer_tokens={"fhir.example.org": "TOKEN"},  # optional per-host auth
)

# Or build it from SOF_RESOLVE_* environment variables:
# config = pysof.RemoteResolveConfig.from_env()

result = pysof.run_view_definition_remote(
    view_definition, bundle, "json", config, fhir_version="R4"
)

# Streaming NDJSON with remote resolve() (one shared cache across chunks):
stats = pysof.process_ndjson_to_file_remote(
    view_definition, "input.ndjson", "output.json", "ndjson", config, chunk_size=1000
)

When config.is_active() is False (disabled or empty allowlist) these behave exactly like their non-remote counterparts. Enabling remote resolution makes output depend on remote server state at run time. See the SQL-on-FHIR guide for the full security model and configuration reference.

Utility Functions

import pysof

# Validate structures
is_valid_view = pysof.validate_view_definition(view_definition)
is_valid_bundle = pysof.validate_bundle(bundle)

# Parse content types
format_str = pysof.parse_content_type("text/csv")  # Returns "csv_with_header"

# Check supported FHIR versions
versions = pysof.get_supported_fhir_versions()  # Returns ["R4"] or more
print(f"Supported FHIR versions: {versions}")

# Package info
print(f"Version: {pysof.get_version()}")
print(pysof.get_status())

Streaming Large NDJSON Files

For memory-efficient processing of large NDJSON files, use the ChunkedProcessor iterator or process_ndjson_to_file function:

import pysof

view_definition = {
    "resourceType": "ViewDefinition",
    "status": "active",
    "resource": "Patient",
    "select": [{"column": [
        {"name": "id", "path": "id"},
        {"name": "gender", "path": "gender"}
    ]}]
}

# Iterator approach - process chunks incrementally
for chunk in pysof.ChunkedProcessor(view_definition, "patients.ndjson", chunk_size=500):
    print(f"Chunk {chunk['chunk_index']}: {len(chunk['rows'])} rows")
    for row in chunk["rows"]:
        process_row(row)
    if chunk["is_last"]:
        print("Processing complete!")

# Access column names before iterating
processor = pysof.ChunkedProcessor(view_definition, "patients.ndjson")
print(f"Columns: {processor.columns}")
for chunk in processor:
    # Process chunks...
    pass

# File-to-file approach - most memory efficient
stats = pysof.process_ndjson_to_file(
    view_definition,
    "input.ndjson",
    "output.csv",
    "csv",  # or "csv_with_header", "ndjson"
    chunk_size=1000,
    skip_invalid=True,  # Continue past invalid JSON lines
    fhir_version="R4"
)
print(f"Processed {stats['resources_processed']} resources")
print(f"Output {stats['output_rows']} rows in {stats['chunks_processed']} chunks")
print(f"Skipped {stats['skipped_lines']} invalid lines")

When to use streaming:

  • Processing NDJSON files larger than available memory
  • Working with datasets of 100K+ resources
  • Building ETL pipelines that process data incrementally
  • When you need fault-tolerant processing (skip invalid lines)

Error Handling

import pysof

try:
    result = pysof.run_view_definition(view_definition, bundle, "json")
except pysof.InvalidViewDefinitionError as e:
    print(f"ViewDefinition validation error: {e}")
except pysof.SerializationError as e:
    print(f"JSON parsing error: {e}")
except pysof.UnsupportedContentTypeError as e:
    print(f"Unsupported format: {e}")
except pysof.SofError as e:
    print(f"General SOF error: {e}")

⚡ Performance

Automatic Parallel Processing

pysof automatically processes FHIR resources in parallel using rayon:

  • 5-7x speedup on typical batch workloads with multi-core CPUs
  • Streaming benefits: ChunkedProcessor and process_ndjson_to_file also use parallel processing
  • Zero configuration - parallelization is always enabled
  • Python GIL released during parsing and processing, so other Python threads stay responsive

Because each call already fans out across all cores via rayon's shared thread pool, running pysof from multiple Python threads does not multiply throughput — one call can saturate the machine. Use Python threads for concurrency (overlapping I/O, serving requests), not to speed up transforms.

Pass Pre-Serialized JSON for Maximum Speed

If your data is already JSON text (from a file, an HTTP body, a database), pass the str or bytes directly instead of json.loads-ing it first:

view_json: str = load_view_definition_text()
bundle_json: bytes = fetch_bundle_bytes()

result = pysof.run_view_definition(view_json, bundle_json, "csv")

This skips the Python-dict conversion entirely and parses the JSON with the GIL released — measured 20-27% faster per call on large bundles, with GIL hold time dropping from tens of milliseconds to microseconds.

Performance Benchmarks

Measured with scripts/bench_threading.py (a 7-column Patient ViewDefinition; Windows 11, 12 logical CPUs, Python 3.11, release build with mimalloc):

Path Dataset Throughput
Batch (dict input) 2,000-patient bundle ~28k patients/sec
Batch (JSON str input) 2,000-patient bundle ~31k patients/sec
Streaming (process_ndjson_to_file) 5,000-patient NDJSON ~31k patients/sec

Numbers vary with hardware and ViewDefinition complexity — re-run scripts/bench_threading.py on your target machine.

Streaming mode (ChunkedProcessor, process_ndjson_to_file) keeps memory bounded by chunk_size regardless of input size, so it is recommended for large NDJSON files; batch mode holds the whole bundle and result in memory.

Controlling Thread Count (RAYON_NUM_THREADS)

Set the RAYON_NUM_THREADS environment variable to control parallel processing:

import os
os.environ['RAYON_NUM_THREADS'] = '4'  # Must be set before first import

import pysof
result = pysof.run_view_definition(view_definition, bundle, "json")

Or from the command line:

# Linux/Mac
RAYON_NUM_THREADS=4 python my_script.py

# Windows PowerShell
$env:RAYON_NUM_THREADS=4
python my_script.py

When to adjust thread count:

  • Reduce threads (RAYON_NUM_THREADS=2-4): On shared systems, containers with CPU limits, or when running multiple instances
  • Increase threads: Rarely needed; rayon auto-detects available cores
  • Single thread (RAYON_NUM_THREADS=1): For debugging or deterministic output ordering

Performance Tips:

  • Use all available cores for large datasets (default behavior)
  • Limit threads on shared systems to avoid resource contention
  • Prefer streaming mode (ChunkedProcessor) for NDJSON files > 100MB

📋 Supported Features

Output Formats

Format Description Output
csv CSV with headers Comma-separated values with header row
json JSON array Array of objects, one per result row
ndjson Newline-delimited JSON One JSON object per line
parquet Parquet format Columnar binary format for analytics

FHIR Versions

  • R4 (default, always available)
  • R4B (if compiled with R4B feature)
  • R5 (if compiled with R5 feature)
  • R6 (if compiled with R6 feature)

Use pysof.get_supported_fhir_versions() to check available versions in your build.


🔧 Development

Requirements

  • Python 3.10 or later (3.10, 3.11, 3.12, 3.13, 3.14 supported)
  • uv (package and environment manager)
  • Rust toolchain (for building from source)

Note: This crate is excluded from the default workspace build. When running cargo build from the repository root, pysof will not be built automatically.

Building from Source

Building with Cargo

This crate is excluded from the default workspace build to allow building the core Rust components without Python. To build it explicitly:

# Your current directory MUST be the pysof crate:
cd crates/pysof

# From the pysof folder
cargo build

# Or build with specific FHIR version features
cargo build -p pysof --features R4,R5

For Python development, it's recommended to use maturin via uv:

# From repo root
cd crates/pysof

# Create a venv with your preferred Python version (3.10+)
uv venv --python 3.11  # or 3.10, 3.12, 3.13, 3.14

# Install the project dev dependencies
uv sync --group dev

# Build and install the Rust extension into the venv
uv run maturin develop --release

# Build distributable artifacts
uv run maturin build --release -o dist     # wheels
uv run maturin sdist -o dist               # source distribution

# Sanity checks
uv run python -c "import pysof; print(pysof.__version__); print(pysof.get_status()); print(pysof.get_supported_fhir_versions())"

Installing from Source

Requires Rust toolchain:

# Install directly
pip install -e .

# Or build wheel locally
maturin build --release --out dist
pip install dist/*.whl

Testing

The project has separate test suites for Python and Rust components:

Python Tests

Run the comprehensive Python test suite:

# Run all Python tests
uv run pytest python-tests/

# Run specific test files
uv run pytest python-tests/test_core_functions.py -v
uv run pytest python-tests/test_content_types.py -v
uv run pytest python-tests/test_import.py -v

# Run with coverage
uv run pytest python-tests/ --cov=pysof --cov-report=html

# Run tests with detailed output
uv run pytest python-tests/ -v --tb=short

Rust Tests

Run the Rust unit and integration tests:

# Run all Rust tests
cargo test

# Run unit tests only
cargo test --test lib_tests

# Run integration tests only
cargo test --test integration

# Run with verbose output
cargo test -- --nocapture

Configuring FHIR Version Support

By default, pysof is compiled with R4 support only. You can configure which FHIR versions are available by modifying the feature compilation settings.

Change Default FHIR Version

To change from R4 to another version (e.g., R5):

  1. Edit crates/pysof/Cargo.toml:

    [features]
    default = ["R5"]  # Changed from ["R4"]
    R4 = ["helios-sof/R4", "helios-fhir/R4"]
    R4B = ["helios-sof/R4B", "helios-fhir/R4B"]
    R5 = ["helios-sof/R5", "helios-fhir/R5"]
    R6 = ["helios-sof/R6", "helios-fhir/R6"]
    
  2. Rebuild the extension:

    cd crates/pysof
    uv run maturin develop --release
    
  3. Verify the change:

    uv run python -c "
    import pysof
    versions = pysof.get_supported_fhir_versions()
    print('Supported FHIR versions:', versions)
    "
    

    This should now show ['R5'] instead of ['R4'].

Enable Multiple FHIR Versions

To support multiple FHIR versions simultaneously:

  1. Edit crates/pysof/Cargo.toml:

    [features]
    default = ["R4", "R5"]  # Enable both R4 and R5
    # Or enable all versions:
    # default = ["R4", "R4B", "R5", "R6"]
    
  2. Rebuild and verify:

    uv run maturin develop --release
    uv run python -c "import pysof; print(pysof.get_supported_fhir_versions())"
    

    This should show ['R4', 'R5'] (or all enabled versions).

  3. Use specific versions in code:

    import pysof
    
    # Use R4 explicitly
    result_r4 = pysof.run_view_definition(view, bundle, "json", fhir_version="R4")
    
    # Use R5 explicitly  
    result_r5 = pysof.run_view_definition(view, bundle, "json", fhir_version="R5")
    

Build with Specific Features (Without Changing Default)

To temporarily build with different features without modifying Cargo.toml:

# Build with only R5
cargo build --features R5 --no-default-features

# Build with R4 and R6
cargo build --features R4,R6 --no-default-features

# With maturin
uv run --with maturin -- maturin develop --release --cargo-extra-args="--features R5 --no-default-features"

Testing After Version Changes

After changing FHIR version support, run the test suite to ensure compatibility:

# Run all tests
uv run pytest

# Run FHIR version-specific tests
uv run pytest tests/test_fhir_versions.py -v

# Test with your new default version
uv run python -c "
import pysof

# Test with default version (should be your new default)
view = {'resourceType': 'ViewDefinition', 'id': 'test', 'name': 'Test', 'status': 'active', 'resource': 'Patient', 'select': [{'column': [{'name': 'id', 'path': 'id'}]}]}
bundle = {'resourceType': 'Bundle', 'type': 'collection', 'entry': [{'resource': {'resourceType': 'Patient', 'id': 'test'}}]}

result = pysof.run_view_definition(view, bundle, 'json')
print('Default version test successful:', len(result), 'bytes')
"

Project layout

crates/pysof/
├─ pyproject.toml          # PEP 621 metadata, Python >=3.8, uv-compatible
├─ README.md
├─ src/
│  ├─ pysof/
│  │  └─ __init__.py       # Python package root
│  └─ lib.rs               # Rust PyO3 bindings
├─ tests/                  # Rust tests (17 tests)
│  ├─ lib_tests.rs         # Unit tests for core library functions
│  ├─ integration.rs       # Integration tests for component interactions
│  └─ integration/         # Organized integration test modules
│     ├─ mod.rs
│     ├─ content_types.rs
│     ├─ error_handling.rs
│     └─ fhir_versions.rs
├─ python-tests/           # Python test suite (58 tests)
│  ├─ __init__.py
│  ├─ test_core_functions.py
│  ├─ test_content_types.py
│  ├─ test_fhir_versions.py
│  ├─ test_import.py
│  └─ test_package_metadata.py
└─ Cargo.toml              # Rust crate metadata

📄 License

MIT License - See LICENSE.md for details.

Copyright (c) 2025 Helios Software

🤝 Contributing

Contributions are welcome! Please see our Contributing Guidelines for details.

Reporting Issues

Development Setup

See the Development section above for instructions on setting up your development environment.

🙏 Acknowledgments

Built with:

  • PyO3 - Rust bindings for Python
  • maturin - Build system for Rust Python extensions
  • helios-sof - Core SQL-on-FHIR implementation in Rust

Part of the Helios FHIR Server project.


Made with ❤️ by Helios Software

Metadata

Release files for pysof 0.2.9

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

Source distribution (sdist)

Source distribution for pysof 0.2.9
File Size Uploaded Provenance Actions
pysof-0.2.9.tar.gz 5.3 MB Without provenance Details for pysof-0.2.9.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for pysof 0.2.9
File Actions
pysof-0.2.9-cp314-cp314-win_amd64.whl CPython 3.14 CPython 3.14 Windows x86-64 Details for pysof-0.2.9-cp314-cp314-win_amd64.whl
pysof-0.2.9-cp314-cp314-manylinux_2_34_x86_64.whl CPython 3.14 CPython 3.14 Linux glibc 2.34+ x86-64 Details for pysof-0.2.9-cp314-cp314-manylinux_2_34_x86_64.whl
pysof-0.2.9-cp314-cp314-manylinux_2_28_aarch64.whl CPython 3.14 CPython 3.14 Linux glibc 2.28+ ARM64 Details for pysof-0.2.9-cp314-cp314-manylinux_2_28_aarch64.whl
pysof-0.2.9-cp314-cp314-macosx_11_0_arm64.whl CPython 3.14 CPython 3.14 macOS 11.0+ ARM64 Details for pysof-0.2.9-cp314-cp314-macosx_11_0_arm64.whl
pysof-0.2.9-cp313-cp313-win_amd64.whl CPython 3.13 CPython 3.13 Windows x86-64 Details for pysof-0.2.9-cp313-cp313-win_amd64.whl
pysof-0.2.9-cp313-cp313-manylinux_2_34_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.34+ x86-64 Details for pysof-0.2.9-cp313-cp313-manylinux_2_34_x86_64.whl
pysof-0.2.9-cp313-cp313-manylinux_2_28_aarch64.whl CPython 3.13 CPython 3.13 Linux glibc 2.28+ ARM64 Details for pysof-0.2.9-cp313-cp313-manylinux_2_28_aarch64.whl
pysof-0.2.9-cp313-cp313-macosx_11_0_arm64.whl CPython 3.13 CPython 3.13 macOS 11.0+ ARM64 Details for pysof-0.2.9-cp313-cp313-macosx_11_0_arm64.whl
pysof-0.2.9-cp312-cp312-win_amd64.whl CPython 3.12 CPython 3.12 Windows x86-64 Details for pysof-0.2.9-cp312-cp312-win_amd64.whl
pysof-0.2.9-cp312-cp312-manylinux_2_34_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.34+ x86-64 Details for pysof-0.2.9-cp312-cp312-manylinux_2_34_x86_64.whl
pysof-0.2.9-cp312-cp312-manylinux_2_28_aarch64.whl CPython 3.12 CPython 3.12 Linux glibc 2.28+ ARM64 Details for pysof-0.2.9-cp312-cp312-manylinux_2_28_aarch64.whl
pysof-0.2.9-cp312-cp312-macosx_11_0_arm64.whl CPython 3.12 CPython 3.12 macOS 11.0+ ARM64 Details for pysof-0.2.9-cp312-cp312-macosx_11_0_arm64.whl
pysof-0.2.9-cp311-cp311-win_amd64.whl CPython 3.11 CPython 3.11 Windows x86-64 Details for pysof-0.2.9-cp311-cp311-win_amd64.whl
pysof-0.2.9-cp311-cp311-manylinux_2_34_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.34+ x86-64 Details for pysof-0.2.9-cp311-cp311-manylinux_2_34_x86_64.whl
pysof-0.2.9-cp311-cp311-manylinux_2_28_aarch64.whl CPython 3.11 CPython 3.11 Linux glibc 2.28+ ARM64 Details for pysof-0.2.9-cp311-cp311-manylinux_2_28_aarch64.whl
pysof-0.2.9-cp311-cp311-macosx_11_0_arm64.whl CPython 3.11 CPython 3.11 macOS 11.0+ ARM64 Details for pysof-0.2.9-cp311-cp311-macosx_11_0_arm64.whl
pysof-0.2.9-cp310-cp310-win_amd64.whl CPython 3.10 CPython 3.10 Windows x86-64 Details for pysof-0.2.9-cp310-cp310-win_amd64.whl
pysof-0.2.9-cp310-cp310-manylinux_2_34_x86_64.whl CPython 3.10 CPython 3.10 Linux glibc 2.34+ x86-64 Details for pysof-0.2.9-cp310-cp310-manylinux_2_34_x86_64.whl
pysof-0.2.9-cp310-cp310-manylinux_2_28_aarch64.whl CPython 3.10 CPython 3.10 Linux glibc 2.28+ ARM64 Details for pysof-0.2.9-cp310-cp310-manylinux_2_28_aarch64.whl
pysof-0.2.9-cp310-cp310-macosx_11_0_arm64.whl CPython 3.10 CPython 3.10 macOS 11.0+ ARM64 Details for pysof-0.2.9-cp310-cp310-macosx_11_0_arm64.whl

Total release size: 645.0 MB

Release files / pysof-0.2.9.tar.gz

Download URL pysof-0.2.9.tar.gz
Size 5.3 MB
Tags Source
SHA-256 checksum
How to use checksums
96dbd04914eaffbcfda794661891db8e2b0853ecdef19fba0acb96558d8c3f30
BLAKE2b-256 checksum
How to use checksums
af97b715aa78d07d8cb57a0942e150c6f6c80bce008b0ea9e667276387035236
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.3

Release files / pysof-0.2.9-cp314-cp314-win_amd64.whl

Download URL pysof-0.2.9-cp314-cp314-win_amd64.whl
Size 36.4 MB
Tags CPython 3.14 Windows x86-64
SHA-256 checksum
How to use checksums
6e2c88cfa56803d9c00b342f5cb3a41e045f1f8b59e191ad34787e88d9cc3112
BLAKE2b-256 checksum
How to use checksums
917d7dbe15d6a69c780c2f0ddf799bf4303504e0901e54ef175241f47a2b87eb
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.3

Release files / pysof-0.2.9-cp314-cp314-manylinux_2_34_x86_64.whl

Download URL pysof-0.2.9-cp314-cp314-manylinux_2_34_x86_64.whl
Size 34.2 MB
Tags CPython 3.14 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
ba4ae59d6f4d3dbd0df8c142dbb1c7e6c6a9ec0972ffaab5c38268dbe7923f5c
BLAKE2b-256 checksum
How to use checksums
662e449e13185781cb2d9889876c1655709185d49091b8f9036885a75f04a8cf
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.3

Release files / pysof-0.2.9-cp314-cp314-manylinux_2_28_aarch64.whl

Download URL pysof-0.2.9-cp314-cp314-manylinux_2_28_aarch64.whl
Size 29.7 MB
Tags CPython 3.14 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
86558d256c457bab3d553c0e2f215e17c2b3b4b096f95c1ba02b341d3a7249d0
BLAKE2b-256 checksum
How to use checksums
4d598c13035039be9cf23ef4df341b08a9bbe0197750a2b24be8cdd10d04af91
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.3

Release files / pysof-0.2.9-cp314-cp314-macosx_11_0_arm64.whl

Download URL pysof-0.2.9-cp314-cp314-macosx_11_0_arm64.whl
Size 27.7 MB
Tags CPython 3.14 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
855488d005ded9499de9ba9def378641d8db1fd2ae8b5a5c4f5bdccfc6583387
BLAKE2b-256 checksum
How to use checksums
e1b56a7fdd1cae9dee44bdda98e368a9b3c249da2f8a48f503c6b4d789b770eb
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.3

Release files / pysof-0.2.9-cp313-cp313-win_amd64.whl

Download URL pysof-0.2.9-cp313-cp313-win_amd64.whl
Size 36.4 MB
Tags CPython 3.13 Windows x86-64
SHA-256 checksum
How to use checksums
93ff3d732eff73e541a3648ca9b1470a072dc1bd42dc313de0d7796083722127
BLAKE2b-256 checksum
How to use checksums
69905e489ae3be6b5656c0ccafdf7f2f9f94db09a57532cb5796bf650a925145
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.3

Release files / pysof-0.2.9-cp313-cp313-manylinux_2_34_x86_64.whl

Download URL pysof-0.2.9-cp313-cp313-manylinux_2_34_x86_64.whl
Size 34.2 MB
Tags CPython 3.13 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
08a7405cb1c40df84be3707e985ad1a7b6f156c7b2b99e4a8716d29ec97b8c03
BLAKE2b-256 checksum
How to use checksums
805de91e2df43e474d7715b325380056b1568b0caca7095435d51955d1ed5980
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.3

Release files / pysof-0.2.9-cp313-cp313-manylinux_2_28_aarch64.whl

Download URL pysof-0.2.9-cp313-cp313-manylinux_2_28_aarch64.whl
Size 29.7 MB
Tags CPython 3.13 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
6ef578dae2f11f0843a14c2e0eb4a41201f7dffca3031713312f87a3529aa2ec
BLAKE2b-256 checksum
How to use checksums
0524c5da0082ca7fb73cfa802406906fb89f30214be498011b903b3a01d98a33
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.3

Release files / pysof-0.2.9-cp313-cp313-macosx_11_0_arm64.whl

Download URL pysof-0.2.9-cp313-cp313-macosx_11_0_arm64.whl
Size 27.7 MB
Tags CPython 3.13 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
976281a3c46ac8478511a6cc36174f582712ae1b4beb9762e3ad69b6ce699b3c
BLAKE2b-256 checksum
How to use checksums
442210fd317e0401025abe1f60e52435ddf80b8f6cb2f86736372b64b8067644
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.3

Release files / pysof-0.2.9-cp312-cp312-win_amd64.whl

Download URL pysof-0.2.9-cp312-cp312-win_amd64.whl
Size 36.4 MB
Tags CPython 3.12 Windows x86-64
SHA-256 checksum
How to use checksums
1047aaf554329fbc32017031832e9c3e6eaa252b7d1d150873719537bbbdb9e7
BLAKE2b-256 checksum
How to use checksums
9770af77c37250b2974a47013aa18ccca3c76b3863c9303f6c68d8efa5cb912f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.3

Release files / pysof-0.2.9-cp312-cp312-manylinux_2_34_x86_64.whl

Download URL pysof-0.2.9-cp312-cp312-manylinux_2_34_x86_64.whl
Size 34.2 MB
Tags CPython 3.12 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
03a5df8775a4083cc8a9446c1668b6974dd46506bf2e4a3783be2f1349e8219d
BLAKE2b-256 checksum
How to use checksums
5f83478909ffca6a0e9b8a47b86cff60e3deff2f5d382203b0130bf33c28ec57
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.3

Release files / pysof-0.2.9-cp312-cp312-manylinux_2_28_aarch64.whl

Download URL pysof-0.2.9-cp312-cp312-manylinux_2_28_aarch64.whl
Size 29.7 MB
Tags CPython 3.12 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
f0c98367496c9ddf4fe60042e8348936ade762d9c4239cfd8c6bc1efa619febd
BLAKE2b-256 checksum
How to use checksums
c7ad564116b7b05d43536c7ad0dc66481d327190b4f4213c22c810437c6e9b74
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.3

Release files / pysof-0.2.9-cp312-cp312-macosx_11_0_arm64.whl

Download URL pysof-0.2.9-cp312-cp312-macosx_11_0_arm64.whl
Size 27.7 MB
Tags CPython 3.12 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
ed220032ba42d7938b868486ef341cc6cddddb441f30c3a1aacd633843f5b8aa
BLAKE2b-256 checksum
How to use checksums
4d14bc91769e2df79f6b3deed82d7e2b52a2040ee64238d2bf4604cf50707b88
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.3

Release files / pysof-0.2.9-cp311-cp311-win_amd64.whl

Download URL pysof-0.2.9-cp311-cp311-win_amd64.whl
Size 36.4 MB
Tags CPython 3.11 Windows x86-64
SHA-256 checksum
How to use checksums
d402cb308060856544b58cd95898fd52f781d24ae788763788a45b3609ba53ed
BLAKE2b-256 checksum
How to use checksums
85cce2f9f77fedf8542b975edf5a16e3d811705353894fd05a124b9af5c71b74
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.3

Release files / pysof-0.2.9-cp311-cp311-manylinux_2_34_x86_64.whl

Download URL pysof-0.2.9-cp311-cp311-manylinux_2_34_x86_64.whl
Size 34.2 MB
Tags CPython 3.11 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
b9ac98ebe216ba508520e9ecf0c5173acffc9db59237104e61ae96ca96963df7
BLAKE2b-256 checksum
How to use checksums
7c64a592ab91878e1870bd5197e0992eb98a994a9317416fd1adae7c719c3359
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.3

Release files / pysof-0.2.9-cp311-cp311-manylinux_2_28_aarch64.whl

Download URL pysof-0.2.9-cp311-cp311-manylinux_2_28_aarch64.whl
Size 29.7 MB
Tags CPython 3.11 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
b1063d1ec02381b45086a8c83cba0f2b2e251f7cd4585cea23cd66f942a56220
BLAKE2b-256 checksum
How to use checksums
c8f75c3cf3fd0d5f4014aecd1e9a7c9e6a2ab6daea3e1f43d16d6d010b4e829e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.3

Release files / pysof-0.2.9-cp311-cp311-macosx_11_0_arm64.whl

Download URL pysof-0.2.9-cp311-cp311-macosx_11_0_arm64.whl
Size 27.7 MB
Tags CPython 3.11 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
e06b447dd3d3a69b2ff0ac34587fc14387eadc48788608e13943101786a2ac2d
BLAKE2b-256 checksum
How to use checksums
39b87ef4ccafcb36078d3dd7577511946093704f5e5fe57894c5698a26350bbc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.3

Release files / pysof-0.2.9-cp310-cp310-win_amd64.whl

Download URL pysof-0.2.9-cp310-cp310-win_amd64.whl
Size 36.4 MB
Tags CPython 3.10 Windows x86-64
SHA-256 checksum
How to use checksums
5d75f714ce159cb1607da5283e4ad433b1a5fe51be51a47b5daaac35fc889a01
BLAKE2b-256 checksum
How to use checksums
084abda31e72598c8b72e6359820e5314425cfa95785380c36a931860c281c03
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.3

Release files / pysof-0.2.9-cp310-cp310-manylinux_2_34_x86_64.whl

Download URL pysof-0.2.9-cp310-cp310-manylinux_2_34_x86_64.whl
Size 34.2 MB
Tags CPython 3.10 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
e8fa8c53781f98bc5ced71d92a5e77592cd59e5f666754d0eb4b4a0d9db84d9a
BLAKE2b-256 checksum
How to use checksums
d10f890c24880492d729df5acc43a3a9eedfa98059bdf3e6b7f03e5bd03edd10
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.3

Release files / pysof-0.2.9-cp310-cp310-manylinux_2_28_aarch64.whl

Download URL pysof-0.2.9-cp310-cp310-manylinux_2_28_aarch64.whl
Size 29.7 MB
Tags CPython 3.10 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
71d53334b3ad370224663912908594ab1ca6010c10cec5d4dae5765f1b9dccb5
BLAKE2b-256 checksum
How to use checksums
6c59368da526bce284e2c7f19f2755a800ba48e730cf096095561465a31237e9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.3

Release files / pysof-0.2.9-cp310-cp310-macosx_11_0_arm64.whl

Download URL pysof-0.2.9-cp310-cp310-macosx_11_0_arm64.whl
Size 27.7 MB
Tags CPython 3.10 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
dd6ba5fa72019db90895033a881b8168cd1b2511ebc47323c99db68c62c4aa31
BLAKE2b-256 checksum
How to use checksums
33c5d552d69d419969738043f58bf6d62f02142347f225bebe0dcba2bdb6cfe4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.13.3

Security for pysof 0.2.9

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.

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