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.7

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.7
File Size Uploaded Provenance Actions
pysof-0.2.7.tar.gz 35.7 MB Without provenance Details for pysof-0.2.7.tar.gz

Built distributions (wheels)

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

Total release size: 684.8 MB

Release files / pysof-0.2.7.tar.gz

Download URL pysof-0.2.7.tar.gz
Size 35.7 MB
Tags Source
SHA-256 checksum
How to use checksums
199ee2bc80c9e490607c0bb0741165ef765562d1a4dec4a7576c80069937b2d8
BLAKE2b-256 checksum
How to use checksums
2cc2ecc3184094a72a4a65491af744214ec111f9abe7da7b7d732c3f041217c4
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.7-cp314-cp314-win_amd64.whl

Download URL pysof-0.2.7-cp314-cp314-win_amd64.whl
Size 35.8 MB
Tags CPython 3.14 Windows x86-64
SHA-256 checksum
How to use checksums
a06984e32a8ba9b7bb82191626be393ce88f32a61a23881578130f72db14377a
BLAKE2b-256 checksum
How to use checksums
62f9e1a80e9679e93320c945b99bc1371eea2b0b82bfd6ca10b7b2016bc96113
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.7-cp314-cp314-manylinux_2_34_x86_64.whl

Download URL pysof-0.2.7-cp314-cp314-manylinux_2_34_x86_64.whl
Size 33.7 MB
Tags CPython 3.14 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
c6b60e70c81b8c09d0d0d916ea9b8d298360810be94c21d4b9bfd8d9a5cf378a
BLAKE2b-256 checksum
How to use checksums
9c16bf0e71f3dbb7c0d962a223f42b2958a1f9dba40809cf954bd0827f99d1c1
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.7-cp314-cp314-manylinux_2_28_aarch64.whl

Download URL pysof-0.2.7-cp314-cp314-manylinux_2_28_aarch64.whl
Size 32.8 MB
Tags CPython 3.14 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
30f169ad70503da7bb226e949c9b866758aafc3a7f53675813ac2a10d7f50861
BLAKE2b-256 checksum
How to use checksums
a540155e0db145654d4befcb79a22ac12c83c0a5a0cd31cc442c673199af3af4
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.7-cp314-cp314-macosx_11_0_arm64.whl

Download URL pysof-0.2.7-cp314-cp314-macosx_11_0_arm64.whl
Size 27.5 MB
Tags CPython 3.14 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
484bded5f976fa09ca88ec4c053d8f0d1084ff7fa82987e4e38ac05e03dab9f3
BLAKE2b-256 checksum
How to use checksums
8b8e1c916a9e51051f84e2c962c6ab5ba5b779f14fcea908bcfe841462e49f93
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.7-cp313-cp313-win_amd64.whl

Download URL pysof-0.2.7-cp313-cp313-win_amd64.whl
Size 35.8 MB
Tags CPython 3.13 Windows x86-64
SHA-256 checksum
How to use checksums
be6a37d74fe3576e63f315c28b1af892f108e38011a04407f6db4f6db59bdea3
BLAKE2b-256 checksum
How to use checksums
f37660d1dbc93bf61d26b90e31970220b1a9af0a04dc7c100ac51a700be5c44c
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.7-cp313-cp313-manylinux_2_34_x86_64.whl

Download URL pysof-0.2.7-cp313-cp313-manylinux_2_34_x86_64.whl
Size 33.7 MB
Tags CPython 3.13 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
ca50a30632d94e83f3a3c2f04849ea3cafca345b07f2ee2bd08d892fb3389ac9
BLAKE2b-256 checksum
How to use checksums
1c932fc09b60460235509a33cd516c0397df5dfa3f880d7c1f895846af331999
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.7-cp313-cp313-manylinux_2_28_aarch64.whl

Download URL pysof-0.2.7-cp313-cp313-manylinux_2_28_aarch64.whl
Size 32.8 MB
Tags CPython 3.13 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
3439c754fe927a8b55765e3d9c4f448cede07133d2e83b7ce09fed0f65a7392b
BLAKE2b-256 checksum
How to use checksums
52fb17141ffef482c7814efb9d24ceee93e1cfe108736337ff998a7484983a1a
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.7-cp313-cp313-macosx_11_0_arm64.whl

Download URL pysof-0.2.7-cp313-cp313-macosx_11_0_arm64.whl
Size 27.5 MB
Tags CPython 3.13 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
3a7d36b9a01127c5f51a8f8a82e0dfb08f791a8d22e4b854b6c7c55d18c2c00c
BLAKE2b-256 checksum
How to use checksums
59b56c4ff6266b1215429edac8cbad746bcadf37a2a0c525cb95ef9d480d40b8
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.7-cp312-cp312-win_amd64.whl

Download URL pysof-0.2.7-cp312-cp312-win_amd64.whl
Size 35.8 MB
Tags CPython 3.12 Windows x86-64
SHA-256 checksum
How to use checksums
fa1892d4d2d7e93d0205a02cf39f24d7eca5e0c11703d288a81d469c9bae01fd
BLAKE2b-256 checksum
How to use checksums
34dc43925c6cf5dffc0c2b410b66f36c8df2bdba5091fadf028be4e21ce472c0
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.7-cp312-cp312-manylinux_2_34_x86_64.whl

Download URL pysof-0.2.7-cp312-cp312-manylinux_2_34_x86_64.whl
Size 33.7 MB
Tags CPython 3.12 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
15193d0213c45e72e117648643c691786fa6f7e8a19b4a088ecaf887eaf7f315
BLAKE2b-256 checksum
How to use checksums
57f257b649a8da785019d44ec5fe43a34cbd48f7e2bb083213e3130b3e645cb2
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.7-cp312-cp312-manylinux_2_28_aarch64.whl

Download URL pysof-0.2.7-cp312-cp312-manylinux_2_28_aarch64.whl
Size 32.8 MB
Tags CPython 3.12 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
28ef507c82b98ac3a221ac6f26fdf74f1d935b5a96e969a1b420771702ebd908
BLAKE2b-256 checksum
How to use checksums
b19b4cc476eb2e280fc1e9a7d855fc394b1510c74e1faba009506099a9af53f2
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.7-cp312-cp312-macosx_11_0_arm64.whl

Download URL pysof-0.2.7-cp312-cp312-macosx_11_0_arm64.whl
Size 27.5 MB
Tags CPython 3.12 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
4657c4f078972bcd1f3a02a3f22a2e19c14c18a375290201de4a789d49bbd876
BLAKE2b-256 checksum
How to use checksums
3b202f7693827f3afbed774ca891a57cca798eb4663bc9c7c04a210ce3b07bc9
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.7-cp311-cp311-win_amd64.whl

Download URL pysof-0.2.7-cp311-cp311-win_amd64.whl
Size 35.8 MB
Tags CPython 3.11 Windows x86-64
SHA-256 checksum
How to use checksums
81e5c8701ed465027dc4bd21fe15dc64cb1c34ee2d18a2763d8ce015c603af17
BLAKE2b-256 checksum
How to use checksums
c18ef325b032942d496c70d093adce27a291c79139d3bbc1bdc697b4909faadc
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.7-cp311-cp311-manylinux_2_34_x86_64.whl

Download URL pysof-0.2.7-cp311-cp311-manylinux_2_34_x86_64.whl
Size 33.7 MB
Tags CPython 3.11 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
8e878a41a23a85b6a0a945ee900019be3b890dd8647f0a3055b2595450fbb88d
BLAKE2b-256 checksum
How to use checksums
2759655d16066c73a6e405aa3f0742ee5bf7bad59e4cba103d82e7d612bb6963
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.7-cp311-cp311-manylinux_2_28_aarch64.whl

Download URL pysof-0.2.7-cp311-cp311-manylinux_2_28_aarch64.whl
Size 32.8 MB
Tags CPython 3.11 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
5aaba519379f1c9656de955132b59eb0ca5d61d99ca0aabf3b2b2dd2535c04a8
BLAKE2b-256 checksum
How to use checksums
56be5d4c42bf3889bdfa2d6b3dc826b5cb7d8c012f535d3189143427ae9101b8
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.7-cp311-cp311-macosx_11_0_arm64.whl

Download URL pysof-0.2.7-cp311-cp311-macosx_11_0_arm64.whl
Size 27.5 MB
Tags CPython 3.11 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
9785f3ba4014279d79b1fbc5c79c3f730515d312fe5e27361117a4a7176af564
BLAKE2b-256 checksum
How to use checksums
b71171c5eb7981c6e7a3abb855849231530f89080018529355080a0f91c37181
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.7-cp310-cp310-win_amd64.whl

Download URL pysof-0.2.7-cp310-cp310-win_amd64.whl
Size 35.8 MB
Tags CPython 3.10 Windows x86-64
SHA-256 checksum
How to use checksums
b4d9f580114aecac48204198555148e7a670888bf8a8746c0c4fd5507b17e0a3
BLAKE2b-256 checksum
How to use checksums
be498b5cf8bf2d3bbc9b464d4b381997bcf64d3a619d1758a2630a12c4f91917
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.7-cp310-cp310-manylinux_2_34_x86_64.whl

Download URL pysof-0.2.7-cp310-cp310-manylinux_2_34_x86_64.whl
Size 33.7 MB
Tags CPython 3.10 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
13a0f874ce81bbc67755389b472c6ebe29281111cccb96c5f69bd450cbc634d0
BLAKE2b-256 checksum
How to use checksums
3be2821e2b54e7e0db6912a48ccf4393b3b5be396ab506a76120686f60549b27
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.7-cp310-cp310-manylinux_2_28_aarch64.whl

Download URL pysof-0.2.7-cp310-cp310-manylinux_2_28_aarch64.whl
Size 32.8 MB
Tags CPython 3.10 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
f34c8dc1b44bb5291a740bfa919a6f44e138854ccaaad4d83743a8a5da31fc9c
BLAKE2b-256 checksum
How to use checksums
c2e74af5874893df3095ffd3a1dcf2d61d72b1210dba44b5e70dbc5447216aaa
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.7-cp310-cp310-macosx_11_0_arm64.whl

Download URL pysof-0.2.7-cp310-cp310-macosx_11_0_arm64.whl
Size 27.5 MB
Tags CPython 3.10 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
1bbee10f62689d905e05a25a9cbe048e5c1e8b256806ce8edc75f434cddb8a49
BLAKE2b-256 checksum
How to use checksums
1a2078005123d27abd3e51fe92141a64f0122711d8d2bc5a7f01deff98b094d4
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.7

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