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

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

Built distributions (wheels)

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

Total release size: 695.6 MB

Release files / pysof-0.2.6.tar.gz

Download URL pysof-0.2.6.tar.gz
Size 36.3 MB
Tags Source
SHA-256 checksum
How to use checksums
01c7df4a1ef1d461110e49b641f166b8ba58239c5945934964ff3e7b3875dd50
BLAKE2b-256 checksum
How to use checksums
23af70c7a2c10d3365349e00151e47320bce55201792e7666ab7e6e10a8e0ef9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.3

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

Download URL pysof-0.2.6-cp314-cp314-win_amd64.whl
Size 36.4 MB
Tags CPython 3.14 Windows x86-64
SHA-256 checksum
How to use checksums
5f631e448198b8c63a61d9145f7c4e98b56cc08855812679b96c56d95a8aa004
BLAKE2b-256 checksum
How to use checksums
5adfa8517b0afa81457740b04b2fd36d6cd5f8a6bc383d5363f41a4d6b523b77
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.3

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

Download URL pysof-0.2.6-cp314-cp314-manylinux_2_34_x86_64.whl
Size 34.3 MB
Tags CPython 3.14 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
37a6ff56d8329df1aed6b96456ea1f8c70ae2a3b253335b68f63c62d1ef3ea99
BLAKE2b-256 checksum
How to use checksums
7b9e542e3af76fbca768b5e213ec5470b7149809734262faab6553b60e3d1b31
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.3

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

Download URL pysof-0.2.6-cp314-cp314-manylinux_2_28_aarch64.whl
Size 33.2 MB
Tags CPython 3.14 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
f26c33df3d2a781eb60d3aa7a963df29e7db49e302284209b75e6a7b832db139
BLAKE2b-256 checksum
How to use checksums
39653187e8ccbb1c443f7bf2e7a372d096ebdc4a7b512c922bea469e0aeb51ec
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.3

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

Download URL pysof-0.2.6-cp314-cp314-macosx_11_0_arm64.whl
Size 28.0 MB
Tags CPython 3.14 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
05ba4dacbea3a5b1e1184774afd2c47b944a2b6319c6a18ffbe71954a8e1704d
BLAKE2b-256 checksum
How to use checksums
96c2b4f4e4b297edecd9b784fc530285bf80d950f1a13e04c704d021952b07e7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.3

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

Download URL pysof-0.2.6-cp313-cp313-win_amd64.whl
Size 36.4 MB
Tags CPython 3.13 Windows x86-64
SHA-256 checksum
How to use checksums
3ad272cc6637a25fb4d6b4adbe56d20adf3daecd6c9a38dcd9fffed24f242457
BLAKE2b-256 checksum
How to use checksums
c4b296a641a4cbf9f48a7b19e84254025fae8974d3ede3ecf601c93a84486bcb
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.3

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

Download URL pysof-0.2.6-cp313-cp313-manylinux_2_34_x86_64.whl
Size 34.3 MB
Tags CPython 3.13 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
2df21a233bef7c3b251ccaf3896e201fa0a97dfd66c56622a9e6ba3018b67395
BLAKE2b-256 checksum
How to use checksums
a117a5d217a210a2db85d093b7b401d6c3edff6588ca3c914cf231cb70dc60e4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.3

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

Download URL pysof-0.2.6-cp313-cp313-manylinux_2_28_aarch64.whl
Size 33.2 MB
Tags CPython 3.13 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
e279e7bfe8a8580e9fbc979cd0acd79e863d479ec6d83f593fdc7af08664ba85
BLAKE2b-256 checksum
How to use checksums
ad72af51a5041c462807a914b61f64447d5c6dbf2a8009182cb5ffb8b3fe743c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.3

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

Download URL pysof-0.2.6-cp313-cp313-macosx_11_0_arm64.whl
Size 28.0 MB
Tags CPython 3.13 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
5651da15616a3e61666a9638df4807053b01b83ace19e099acff478571eff747
BLAKE2b-256 checksum
How to use checksums
825a53d77d9fb0de33709fcf9863fb5d21da5a0ee5952071d55de57ea75ab82c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.3

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

Download URL pysof-0.2.6-cp312-cp312-win_amd64.whl
Size 36.4 MB
Tags CPython 3.12 Windows x86-64
SHA-256 checksum
How to use checksums
c1db5f679ff0b7d48a9a38572e52e71bb7bcf79b5edbeae96b218560ce2d1680
BLAKE2b-256 checksum
How to use checksums
6c63f69078722e05d530cbefc9b36dd67328f2f0abe7c7780f192c18521f35eb
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.3

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

Download URL pysof-0.2.6-cp312-cp312-manylinux_2_34_x86_64.whl
Size 34.3 MB
Tags CPython 3.12 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
83747ccc3fa16a00adeebc8859610576a4acdf1f6f088a566eaceb59859712d7
BLAKE2b-256 checksum
How to use checksums
b315651713b594eb7f84205a46df5625b2e96158cb78b5a222b31582722c8262
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.3

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

Download URL pysof-0.2.6-cp312-cp312-manylinux_2_28_aarch64.whl
Size 33.2 MB
Tags CPython 3.12 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
d8c09fe0a4e8e72c01c4884ea1170aa076c2aeaec171130401a788aecca28d5f
BLAKE2b-256 checksum
How to use checksums
8b970bc5ac1e83b1ffc4adc6a4886d1409ed0003a91b9d9d3b98b7a9efffbfec
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.3

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

Download URL pysof-0.2.6-cp312-cp312-macosx_11_0_arm64.whl
Size 28.0 MB
Tags CPython 3.12 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
a1c638301d895145b0e608734cf9ad63e1c354c1ae377cdd006e293d5b157a79
BLAKE2b-256 checksum
How to use checksums
8ccb44746e31d15153bd9c33975da58e59d81317a737f4aef11f091d389400ba
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.3

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

Download URL pysof-0.2.6-cp311-cp311-win_amd64.whl
Size 36.4 MB
Tags CPython 3.11 Windows x86-64
SHA-256 checksum
How to use checksums
69968555b71bf9a6f1aeb4d6c3a8486822f56e3a02c5aa8af9cc2a554d92b3b9
BLAKE2b-256 checksum
How to use checksums
7a53abbf1dd7fae2d53d2f662821b9a037e5e87e62f351212e9420dd036d9aa8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.3

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

Download URL pysof-0.2.6-cp311-cp311-manylinux_2_34_x86_64.whl
Size 34.3 MB
Tags CPython 3.11 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
cf9ea06d33eba539c3372a445d9adc76495eb8a917d543d9c28aa2105e47f87e
BLAKE2b-256 checksum
How to use checksums
bb8aa9b162cd1f608dd36c6323448146f0e353238e4c5c7e3938c3096615bb6d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.3

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

Download URL pysof-0.2.6-cp311-cp311-manylinux_2_28_aarch64.whl
Size 33.2 MB
Tags CPython 3.11 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
76a5200ac05401ccdaa47b283f391e988c47a13b8248dada910c6c54b039cc21
BLAKE2b-256 checksum
How to use checksums
3b870ce71e0e1dc1cc39af55f83ceb741ccfa1ee5ac185baa8b53592b5812290
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.3

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

Download URL pysof-0.2.6-cp311-cp311-macosx_11_0_arm64.whl
Size 28.0 MB
Tags CPython 3.11 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
d3125cd94e7634aeb3e5dd3dca1bef729cd4475fd64d1d2750d0112d1f1767f9
BLAKE2b-256 checksum
How to use checksums
429a272d15e6e933fb7d9a4301577245c09ea96fe6d9b01a9f758508608ece06
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.3

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

Download URL pysof-0.2.6-cp310-cp310-win_amd64.whl
Size 36.4 MB
Tags CPython 3.10 Windows x86-64
SHA-256 checksum
How to use checksums
242a57561a3dd388d17d4cc8fba45246fef486537c9fbf545d74094ee1e5f574
BLAKE2b-256 checksum
How to use checksums
59751d0bc128217946007d99ff75c2021336f2c5787eb068e58dc0b8252da7af
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.3

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

Download URL pysof-0.2.6-cp310-cp310-manylinux_2_34_x86_64.whl
Size 34.3 MB
Tags CPython 3.10 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
c4a754662d49393624dff837b89431ee84de5de9b5acf1ce06de5aca349921ca
BLAKE2b-256 checksum
How to use checksums
5d104b291a26a1ae077d395b4a482f89043af0458cef95b613c0d8c694144ef9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.3

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

Download URL pysof-0.2.6-cp310-cp310-manylinux_2_28_aarch64.whl
Size 33.2 MB
Tags CPython 3.10 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
24daac540bafea19d808d52ad965c0b9e369d35cef6d27260a43b7edac89e16e
BLAKE2b-256 checksum
How to use checksums
f9229c5e809358dd2fbccfc51d6b5729d9eedfb78f2f1e646818ed6c5b38c4da
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.3

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

Download URL pysof-0.2.6-cp310-cp310-macosx_11_0_arm64.whl
Size 28.0 MB
Tags CPython 3.10 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
2f059f544d43c1a0f341f1823e1214b2783f03d7820d7d6087d5bae643050feb
BLAKE2b-256 checksum
How to use checksums
4e910c4c0bc86fe75e1ef52c01beca4424420d1cf451d1d6d384d5fe6e70adf8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.3

Security for pysof 0.2.6

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