Skip to main content

UnifyVcf

Unifies the separate structural call files a sequencing pipeline produces into the single VCF Geneyx reads as an SV VCF.

The files it unifies are:

  • SV – structural variants VCF
  • CNV – copy number variants VCF
  • Repeats – tandem repeat variants VCF
  • ROH – Regions of Homozygosity (DRAGEN BED, or an already-converted VCF)

It does not only concatenate them. Each caller writes slightly different files, and Geneyx needs specific fields to read a record properly — so records are rewritten on the way out and the result is sorted and bgzipped. Run the entry point that matches the pipeline your VCFs came from.

This package is the single implementation behind both the customer-facing scripts in geneyx.analysis.api and the Geneyx primary pipeline, so both produce the same unified file.

Installation

pip install UnifyVcf

Python 3.9–3.13 on Linux, macOS or Windows, with no external tools required and no dependencies outside the standard library. Sorting and BGZF compression are pure Python; repeat filtering uses bedtools when it is installed and computes the same intersection itself when it is not.

Wheels are published per platform and Python version because the implementation ships compiled — see How this is distributed. If pip install reports no matching distribution, your platform or Python version is outside the published set; tell us which and we will add it.

Command line

dragen-unify-vcf  -o OUTPUTPATH [-s SVPATH] [-c CNVPATH] [-r REPEATPATH] [-d ROH_BED_FILE]
ont-unify-vcf     -o OUTPUTPATH [-s SVPATH] [-c CNVPATH] [-r REPEATPATH] [-modify]
pacbio-unify-vcf  -o OUTPUTPATH [-s SVPATH] [-c CNVPATH] [-r FULLREPEATPATH] [-b REPEATLOCATIONSBEDFILEPATH]
Argument Meaning
-o Path to the unified VCF, including its name. The output is compressed, so the name should end in .vcf, not .gz.
-s Structural variants (SV) VCF. Gzipped or not.
-c Copy number variants (CNV) VCF. Gzipped or not.
-r Tandem repeats VCF. Gzipped or not.
-d DRAGEN only. The ROH BED produced by DRAGEN when run with --vc-enable-roh.
-modify ONT only, and no longer needed. Forces ;SVTYPE=REP onto every repeat call. Without it, a repeat call that carries no SVTYPE is marked anyway and one that already has one is left alone.
-b PacBio only. A BED restricting which repeat loci are unified. Without -b the repeats are left out of the unified file entirely, because the full TRGT catalog is far wider than a report can interpret.

A catalog of pathogenic hg38 STR loci ships with the package:

from UnifyVcf import default_repeat_catalog_path
pacbio-unify-vcf -o unified.vcf -s sv.vcf.gz \
  -r sample.GRCh38.trgt.sorted.vcf.gz \
  -b "$(python -c 'from UnifyVcf import default_repeat_catalog_path as p; print(p())')"

Python

from UnifyVcf import run

run(output_path="unified.vcf", sv_path="sv.vcf.gz", cnv_path="cnv.vcf.gz",
    repeat_path="repeats.vcf.gz", roh_bed_path="roh.bed")

run keeps the signature the standalone UnifyVcf.py script published, so code that did from UnifyVcf import run works unchanged once this package is installed.

A caller that already owns a sorting step — the Geneyx pipeline does — skips run and composes the pieces instead, so it keeps its own sorting and indexing:

from UnifyVcf import UnifyOptions, read_struct_lines, unify_lines

options = UnifyOptions(drop_sv_filters=("InvBreakpoint",))  # exclude by FILTER
unify_lines(read_struct_lines(paths, options), "unified.vcf", options)   # unsorted

Nothing about the shape of the inputs has to be declared. Whether a repeat record needs ;SVTYPE=REP is read off the record, and whether ROH arrived as a BED or an already-converted VCF is read off the file — so the same call is correct for DRAGEN, ONT and PacBio input. UnifyOptions still accepts add_repeat_svtype and roh_format as overrides for a caller that knows better than its files do.

How the pieces fit

Function Does
read_struct_lines(paths, options) Reads each input (gzipped or not), drops excluded SV records, and skips inputs that are empty or header-only.
unify_lines(lines, output_path, options) Writes the unified, unsorted VCF. Returns None when there was nothing to write.
sort_and_compress(vcf_path) Sorts by position and bgzips; returns the .gz path.
filter_repeats_vcf(repeat_path, bed_path) Intersects a repeat VCF with a locus catalog, via bedtools or in Python.

PacBio has two front doors over these, because repeat filtering is separable: pacbio_filter_and_unify filters the full TRGT VCF against a catalog and then unifies, which is what pacbio-unify-vcf runs; pacbio_unify unifies repeats that are already filtered, for a caller that owns that step itself.

The first present input in SV → CNV → repeats order donates the header; the rest contribute records only.

Platform support

Everything runs on Linux, macOS and Windows. Two things used to be Linux-only and are no longer:

Sorting and compression. The output has to be sorted by position and compressed as BGZF — a gzip variant written in <64KB blocks — because Geneyx indexes it with tabix, and tabix cannot index plain gzip. Compression is always pure Python. Sorting has two engines: a pure-Python one that needs no sort binary, and one that shells out to a real sort -k1,1 -k2,2n — several times faster past a few hundred thousand records, which a PacBio long-read callset can reach. sort_and_compress prefers the sort binary when it is on PATH, the same way repeat filtering below prefers bedtools. Either way the ordering matches what sort -k1,1 -k2,2n produced under the previous shell implementation, including GNU sort's whole-line tie-break, so files keep the order Geneyx has always received — tests/test_sort_parity.py pins the two engines against each other to prove it.

Repeat filtering. bedtools intersect is used where bedtools is on PATH. Where it is not, the same intersection is computed in Python: a record spans [POS-1, END), taking END from INFO where present — repeat callers emit symbolic <STR> alleles whose length is not the length of REF — and falling back to POS-1 + len(REF). The engine that ran is logged. The CI runs the suite on both Linux and Windows, and the Linux leg installs bedtools so the two engines are compared against each other rather than one being skipped.

Force one or the other when you need to:

from UnifyVcf import BEDTOOLS, BUILTIN, filter_repeats_vcf

filter_repeats_vcf(repeats, catalog, engine=BUILTIN)
from UnifyVcf import GNU_SORT, PYTHON_SORT, sort_and_compress

sort_and_compress(unified_vcf_path, engine=PYTHON_SORT)

How this is distributed

The wheel ships compiled modules (.pyd on Windows, .so elsewhere), not .py files. What it publishes instead is the interface:

  • UnifyVcf/*.pyi type stubs carrying every public signature and its description, generated from the source by tools/generate_stubs.py
  • the same docstrings inside the compiled modules, so help(UnifyVcf.run) works
  • py.typed, so mypy and IDEs read the stubs
  • this README

So autocomplete, type checking and help() behave normally; the function bodies are just not there to read. __init__.py stays interpreted deliberately — it is only re-exports, and it is the surface this README documents.

Consequences worth knowing:

  • No sdist is published. An sdist would carry the sources, undoing the point. pip download --no-binary :all: therefore has nothing to fetch.

  • One wheel per platform and Python version, built by cibuildwheel in CI, rather than the single pure-Python wheel a normal package gets.

  • Import from UnifyVcf, not from its submodules. Pylint will not import an extension module to see what it exports, and it does not read the stubs, so a perfectly good from UnifyVcf.cli import dragen_from_cli is reported as E0611: No name 'dragen_from_cli' in module 'UnifyVcf.cli'. __init__.py stays interpreted, so pylint reads the names straight out of it and from UnifyVcf import dragen_from_cli analyses cleanly — which is why everything public is re-exported there. A caller that does need a submodule directly wants this in its pylint config:

    [MAIN]
    extension-pkg-allow-list=UnifyVcf
    

    mypy and Pylance need neither, they read the stubs.

  • This is a deterrent, not a control. A compiled extension can still be analysed, and string literals — log messages, ;SVTYPE=REP and the like — remain visible in the binary because the code has to use them at run time. It stops casual reading and copy-paste reuse; it is not a security boundary.

Working on the package

The sources live in this repository and run interpreted, so development and the test suite are unaffected:

pip install -e .            # needs a C compiler; builds the extensions in place
python -m pytest tests
python tools/generate_stubs.py          # after changing any public signature
python tools/generate_stubs.py --check  # what CI enforces

tests/test_published_surface.py fails if a stub drifts from the source, so the published description cannot silently stop matching the code.

Per-caller differences

These are options rather than separate implementations:

DRAGEN ONT PacBio Geneyx pipeline
;SVTYPE=REP on repeats detected detected detected detected
ROH input detected – – detected
Repeat filtering – – bedtools against -b done as its own pipeline step
SV FILTER exclusions none none none InvBreakpoint (PacBio)

The first two rows used to be per-caller options and are now read off the files, so those callers no longer differ at all. The third is the same filter_repeats_vcf call on both sides, made at a different point — see the two PacBio front doors above.

The last row is a real difference and not one this package can resolve: a customer unifying their own PacBio VCFs keeps InvBreakpoint records, and the pipeline drops them, so the same SV callset yields a different reported call set depending on which path unified it. Whether a breakpoint half of an inversion is a reportable event is a product decision, and it is listed here to stay visible until it is made.

The PacBio row and the pipeline row differ on InvBreakpoint deliberately: the Geneyx pipeline drops those records from the unified file it analyses, and the customer-facing script does not. Aligning them would change what customers upload, so it is a product decision rather than a packaging one.

Known defect carried over

Pinned by a characterization test rather than fixed, so that packaging stayed a refactor. Worth its own change:

is_valid_line misses single-sample no-calls. The GT is read from the last tab-separated cell, which on a single-sample record still carries the trailing newline, so "./.\n" != "./." and the no-call is kept. Multi-sample records take the intended path. The neighbouring gt_index == '0' compares an int to a str and is never true.

Two other defects in the original shell-based sorter are gone as a consequence of rewriting it for Windows, rather than by choice:

  • It swallowed its own failures — a failed sort or bgzip was logged and execution continued, leaving an unsorted, uncompressed .vcf where the caller expected .vcf.gz. Failures now raise.
  • Its temp directory was vcf-temp in the current working directory, so two runs in one directory deleted each other's temp files. Temporary files are now written beside the output and removed in a finally.

Tests

pytest tests

No bedtools, bgzip or network needed — the suite is file manipulation only. One test compares the two repeat-filtering engines and skips where bedtools is not installed.

Metadata

Release files for UnifyVcf 0.2.1

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

Built distributions (wheels)

Table of built distributions (wheels) for UnifyVcf 0.2.1
File Actions
unifyvcf-0.2.1-cp314-cp314-win_amd64.whl CPython 3.14 CPython 3.14 Windows x86-64 Details for unifyvcf-0.2.1-cp314-cp314-win_amd64.whl
unifyvcf-0.2.1-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.14 CPython 3.14 Linux glibc 2.28+ x86-64, Linux glibc 2.17+ x86-64 Details for unifyvcf-0.2.1-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
unifyvcf-0.2.1-cp314-cp314-macosx_10_15_x86_64.whl CPython 3.14 CPython 3.14 macOS 10.15+ x86-64 Details for unifyvcf-0.2.1-cp314-cp314-macosx_10_15_x86_64.whl
unifyvcf-0.2.1-cp313-cp313-win_amd64.whl CPython 3.13 CPython 3.13 Windows x86-64 Details for unifyvcf-0.2.1-cp313-cp313-win_amd64.whl
unifyvcf-0.2.1-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.28+ x86-64, Linux glibc 2.17+ x86-64 Details for unifyvcf-0.2.1-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
unifyvcf-0.2.1-cp313-cp313-macosx_10_13_x86_64.whl CPython 3.13 CPython 3.13 macOS 10.13+ x86-64 Details for unifyvcf-0.2.1-cp313-cp313-macosx_10_13_x86_64.whl
unifyvcf-0.2.1-cp312-cp312-win_amd64.whl CPython 3.12 CPython 3.12 Windows x86-64 Details for unifyvcf-0.2.1-cp312-cp312-win_amd64.whl
unifyvcf-0.2.1-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.28+ x86-64, Linux glibc 2.17+ x86-64 Details for unifyvcf-0.2.1-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
unifyvcf-0.2.1-cp312-cp312-macosx_10_13_x86_64.whl CPython 3.12 CPython 3.12 macOS 10.13+ x86-64 Details for unifyvcf-0.2.1-cp312-cp312-macosx_10_13_x86_64.whl
unifyvcf-0.2.1-cp311-cp311-win_amd64.whl CPython 3.11 CPython 3.11 Windows x86-64 Details for unifyvcf-0.2.1-cp311-cp311-win_amd64.whl
unifyvcf-0.2.1-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for unifyvcf-0.2.1-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
unifyvcf-0.2.1-cp311-cp311-macosx_10_9_x86_64.whl CPython 3.11 CPython 3.11 macOS 10.9+ x86-64 Details for unifyvcf-0.2.1-cp311-cp311-macosx_10_9_x86_64.whl
unifyvcf-0.2.1-cp310-cp310-win_amd64.whl CPython 3.10 CPython 3.10 Windows x86-64 Details for unifyvcf-0.2.1-cp310-cp310-win_amd64.whl
unifyvcf-0.2.1-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.10 CPython 3.10 Linux glibc 2.28+ x86-64, Linux glibc 2.17+ x86-64 Details for unifyvcf-0.2.1-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
unifyvcf-0.2.1-cp310-cp310-macosx_10_9_x86_64.whl CPython 3.10 CPython 3.10 macOS 10.9+ x86-64 Details for unifyvcf-0.2.1-cp310-cp310-macosx_10_9_x86_64.whl
unifyvcf-0.2.1-cp39-cp39-win_amd64.whl CPython 3.9 CPython 3.9 Windows x86-64 Details for unifyvcf-0.2.1-cp39-cp39-win_amd64.whl
unifyvcf-0.2.1-cp39-cp39-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.9 CPython 3.9 Linux glibc 2.28+ x86-64, Linux glibc 2.17+ x86-64 Details for unifyvcf-0.2.1-cp39-cp39-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
unifyvcf-0.2.1-cp39-cp39-macosx_10_9_x86_64.whl CPython 3.9 CPython 3.9 macOS 10.9+ x86-64 Details for unifyvcf-0.2.1-cp39-cp39-macosx_10_9_x86_64.whl

Total release size: 11.8 MB

Release files / unifyvcf-0.2.1-cp314-cp314-win_amd64.whl

Download URL unifyvcf-0.2.1-cp314-cp314-win_amd64.whl
Size 211.2 kB
Tags CPython 3.14 Windows x86-64
SHA-256 checksum
How to use checksums
a341a99a8d046d5685c7f76b7b3f08d355a5ac4a1a560f1762d918255d892b87
BLAKE2b-256 checksum
How to use checksums
9962a79339da28087f2bb5d3b3cdbea7620c593387415c9021950699ee54bad3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.16

Release files / unifyvcf-0.2.1-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL unifyvcf-0.2.1-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 1.5 MB
Tags CPython 3.14 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
8299db5b248dc1570813b3f5e1d9d313782891eed9b8daf991bbdd888ed805af
BLAKE2b-256 checksum
How to use checksums
09fd88dfef81f39613591ec987ad4975548b2dfb96b8e519135898075a302b97
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.16

Release files / unifyvcf-0.2.1-cp314-cp314-macosx_10_15_x86_64.whl

Download URL unifyvcf-0.2.1-cp314-cp314-macosx_10_15_x86_64.whl
Size 243.5 kB
Tags CPython 3.14 macOS 10.15+ x86-64
SHA-256 checksum
How to use checksums
eb2fbb45719e3c896f5f6be9c1909360940fdb0ae02ff2d2941884d2ecbaad5b
BLAKE2b-256 checksum
How to use checksums
23b9e44a0ff67d302f25048a6b5799f37343ddeb70fd9db92fb53d9520451e05
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.16

Release files / unifyvcf-0.2.1-cp313-cp313-win_amd64.whl

Download URL unifyvcf-0.2.1-cp313-cp313-win_amd64.whl
Size 208.4 kB
Tags CPython 3.13 Windows x86-64
SHA-256 checksum
How to use checksums
2ad1ed73406e0371d6d6a2d44a596318737f20340290682472a640cbd5602b27
BLAKE2b-256 checksum
How to use checksums
f9810711e5bd8ae7fa8a980b121e870bd28c0fc3384633af23a748c3353e3732
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.16

Release files / unifyvcf-0.2.1-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL unifyvcf-0.2.1-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 1.5 MB
Tags CPython 3.13 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
17b196d4e5279094b676678022c00d5c8612230c81afe0b8bd5748d6a15847a1
BLAKE2b-256 checksum
How to use checksums
a011882e16d5bf257ff545c69e78d6b58c0b55bfdabad5967b9e8265fed14810
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.16

Release files / unifyvcf-0.2.1-cp313-cp313-macosx_10_13_x86_64.whl

Download URL unifyvcf-0.2.1-cp313-cp313-macosx_10_13_x86_64.whl
Size 243.6 kB
Tags CPython 3.13 macOS 10.13+ x86-64
SHA-256 checksum
How to use checksums
8a3f7c567800e4c9a2c750391739122c5c6667e8e6f7ee566c493205cf7b3f1b
BLAKE2b-256 checksum
How to use checksums
ae99cf0cb3be4127c53acdbcebba1d983a32103c59c0821e176c22097baf43a4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.16

Release files / unifyvcf-0.2.1-cp312-cp312-win_amd64.whl

Download URL unifyvcf-0.2.1-cp312-cp312-win_amd64.whl
Size 209.7 kB
Tags CPython 3.12 Windows x86-64
SHA-256 checksum
How to use checksums
db2a8009b860c94b4c66cf36e9618c05234078d4442c41c26c2f616ad2ab7297
BLAKE2b-256 checksum
How to use checksums
c3d7e1f3116d6f56f3036a7a8b8769c52d30708d926ce421b2f894889d3db9f5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.16

Release files / unifyvcf-0.2.1-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL unifyvcf-0.2.1-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 1.6 MB
Tags CPython 3.12 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
2d1d9ca93e262d29df6a17e2e5c1ddbd99fc3c16f9fbc073dd8a546bd7dc8d4f
BLAKE2b-256 checksum
How to use checksums
deda7dc67a808cfd76722a5f10443bb1444729e50a4fe9bdbe63dc26270bbf89
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.16

Release files / unifyvcf-0.2.1-cp312-cp312-macosx_10_13_x86_64.whl

Download URL unifyvcf-0.2.1-cp312-cp312-macosx_10_13_x86_64.whl
Size 244.6 kB
Tags CPython 3.12 macOS 10.13+ x86-64
SHA-256 checksum
How to use checksums
9b8e56fd239bfdbc82fbb19b358942c9cb525bf05d05f5c41a0cf89fd877be42
BLAKE2b-256 checksum
How to use checksums
9343775fb8b739bec129dd992ed269ff76fd963720ce2c6f71906d736c6c9d8b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.16

Release files / unifyvcf-0.2.1-cp311-cp311-win_amd64.whl

Download URL unifyvcf-0.2.1-cp311-cp311-win_amd64.whl
Size 215.9 kB
Tags CPython 3.11 Windows x86-64
SHA-256 checksum
How to use checksums
7c9d4c7ea89ef1828166925fe570a8a53dd8eb978763b3f657c81ee1d62e1b58
BLAKE2b-256 checksum
How to use checksums
0996829284175efdbe66be79f5e76f837eb34e3e8356564fd361b718bf76dfa3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.16

Release files / unifyvcf-0.2.1-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL unifyvcf-0.2.1-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 1.5 MB
Tags CPython 3.11 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
b5d6edb1410c27493aba2e2c7316f7e77761c14b3340a83395bdb879a8d43f4e
BLAKE2b-256 checksum
How to use checksums
9efb20fdb06b0612d56fcd8841326d670327c9e2f5aeaf44cbc2b46e499d3ff7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.16

Release files / unifyvcf-0.2.1-cp311-cp311-macosx_10_9_x86_64.whl

Download URL unifyvcf-0.2.1-cp311-cp311-macosx_10_9_x86_64.whl
Size 241.4 kB
Tags CPython 3.11 macOS 10.9+ x86-64
SHA-256 checksum
How to use checksums
6e1d0ef227c8934a392f07f5a3b35d810dfb3eb984faab589a184d8f5a46bd8c
BLAKE2b-256 checksum
How to use checksums
f7ad4a18bea525471969d8eeb8ae4fcee968087169f4650a311057fc4866292b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.16

Release files / unifyvcf-0.2.1-cp310-cp310-win_amd64.whl

Download URL unifyvcf-0.2.1-cp310-cp310-win_amd64.whl
Size 216.9 kB
Tags CPython 3.10 Windows x86-64
SHA-256 checksum
How to use checksums
5534347a68df45b2a77f4caf3d067b4b78cc842955beda642daeb943f38bda3a
BLAKE2b-256 checksum
How to use checksums
520c666f87fa400bd1a11f786f4ff652dccb2dc81a652213312610c0be47a623
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.16

Release files / unifyvcf-0.2.1-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL unifyvcf-0.2.1-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 1.5 MB
Tags CPython 3.10 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
219c94760810cfd9aa330614d2c033f054d37c0500e4c952e139b3952ebf7c02
BLAKE2b-256 checksum
How to use checksums
0765567b8e069953749d64baa319b173a5359dbbb7a7483749a05eb61cd9e453
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.16

Release files / unifyvcf-0.2.1-cp310-cp310-macosx_10_9_x86_64.whl

Download URL unifyvcf-0.2.1-cp310-cp310-macosx_10_9_x86_64.whl
Size 245.3 kB
Tags CPython 3.10 macOS 10.9+ x86-64
SHA-256 checksum
How to use checksums
ab8ae18685d7472e45f34362782781a380d9285a6b530ccda89bcacf65176ac7
BLAKE2b-256 checksum
How to use checksums
500bcc55573acba8d96497f036d4cb36394fb326855cc73b0a17c6e1b4e08e86
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.16

Release files / unifyvcf-0.2.1-cp39-cp39-win_amd64.whl

Download URL unifyvcf-0.2.1-cp39-cp39-win_amd64.whl
Size 217.7 kB
Tags CPython 3.9 Windows x86-64
SHA-256 checksum
How to use checksums
1a3010a3b3156d83ae9b5367286042afdfa78be31c901c726cb646571bfc6731
BLAKE2b-256 checksum
How to use checksums
bd060266f54f682c98a6f27885b50cc64aba01b9f80c00765bf153d85dad6d92
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.16

Release files / unifyvcf-0.2.1-cp39-cp39-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL unifyvcf-0.2.1-cp39-cp39-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 1.5 MB
Tags CPython 3.9 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
154f411406dc4435c0794a981242dbba12302b9f7ca70d8c5f0209d17cbad6a1
BLAKE2b-256 checksum
How to use checksums
24dcfb8ffc22dbe3ee4a62b85357fd959e3f332ed23d5719eebb359a91af0d38
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.16

Release files / unifyvcf-0.2.1-cp39-cp39-macosx_10_9_x86_64.whl

Download URL unifyvcf-0.2.1-cp39-cp39-macosx_10_9_x86_64.whl
Size 246.6 kB
Tags CPython 3.9 macOS 10.9+ x86-64
SHA-256 checksum
How to use checksums
b67b3bdd3388a45f2b20eed110bb90a0086f37610f1a79608b4cf6b2ba174354
BLAKE2b-256 checksum
How to use checksums
52a38231b19a7904d6cf83c39c0fa525259368e8e68f9472c93fe12a75996be3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.16

Security for UnifyVcf 0.2.1

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