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 (the ROH BED DRAGEN or bcftools roh wrote, 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] [-d ROH_BED_FILE]

A fourth entry point merges small variants rather than structural calls (GAN-8963):

dragen-unify-snv-vcf  -o OUTPUTPATH [-s SNVPATH] [-t TARGETPATH]

-s is the DRAGEN SNV VCF and -t the targeted-caller VCF (target.vcf), whose records carry the joint genotype fields JGT, JGQ, JDP and JAD. The SNV header is kept and any header line only the target declares is added to it. DRAGEN's own hard-filtered VCF already carries the targeted calls, flagged TARGETED in INFO, so a flagged SNV record at the same CHROM/POS/REF/ALT as a target record is replaced by it; regular-caller records at that site are kept. Either input may be omitted. The result is sorted and bgzipped. From Python: from UnifyVcf import dragen_snv_unify.

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 and PacBio. The ROH BED: the one DRAGEN writes under --vc-enable-roh, or the one bcftools roh writes in the PacBio HiFi workflow (<sample>.GRCh38.bcftools_roh.bed, #chr start end qual header included). Each interval becomes an <ROH> record; one without a score gets ROH_SCORE=., and a line that is not an interval is skipped and counted in the log.
-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())')" \
  -d sample.GRCh38.bcftools_roh.bed

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 detected
Repeat filtering – – bedtools against -b the same, in its unify 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 pipeline's unify step filters against its configured catalog, keeps the filtered file as a delivered artefact, and hands the ROH BED straight to the unifier — the BED-to-VCF conversion that used to be a pipeline step of its own is this package's, so a BED passed in and a VCF converted from it first unify to the same records.

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

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.3
File Actions
unifyvcf-0.2.3-cp314-cp314-win_amd64.whl CPython 3.14 CPython 3.14 Windows x86-64 Details for unifyvcf-0.2.3-cp314-cp314-win_amd64.whl
unifyvcf-0.2.3-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.17+ x86-64, Linux glibc 2.28+ x86-64 Details for unifyvcf-0.2.3-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
unifyvcf-0.2.3-cp314-cp314-macosx_10_15_x86_64.whl CPython 3.14 CPython 3.14 macOS 10.15+ x86-64 Details for unifyvcf-0.2.3-cp314-cp314-macosx_10_15_x86_64.whl
unifyvcf-0.2.3-cp313-cp313-win_amd64.whl CPython 3.13 CPython 3.13 Windows x86-64 Details for unifyvcf-0.2.3-cp313-cp313-win_amd64.whl
unifyvcf-0.2.3-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.3-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
unifyvcf-0.2.3-cp313-cp313-macosx_10_13_x86_64.whl CPython 3.13 CPython 3.13 macOS 10.13+ x86-64 Details for unifyvcf-0.2.3-cp313-cp313-macosx_10_13_x86_64.whl
unifyvcf-0.2.3-cp312-cp312-win_amd64.whl CPython 3.12 CPython 3.12 Windows x86-64 Details for unifyvcf-0.2.3-cp312-cp312-win_amd64.whl
unifyvcf-0.2.3-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.3-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
unifyvcf-0.2.3-cp312-cp312-macosx_10_13_x86_64.whl CPython 3.12 CPython 3.12 macOS 10.13+ x86-64 Details for unifyvcf-0.2.3-cp312-cp312-macosx_10_13_x86_64.whl
unifyvcf-0.2.3-cp311-cp311-win_amd64.whl CPython 3.11 CPython 3.11 Windows x86-64 Details for unifyvcf-0.2.3-cp311-cp311-win_amd64.whl
unifyvcf-0.2.3-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.28+ x86-64, Linux glibc 2.17+ x86-64 Details for unifyvcf-0.2.3-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
unifyvcf-0.2.3-cp311-cp311-macosx_10_9_x86_64.whl CPython 3.11 CPython 3.11 macOS 10.9+ x86-64 Details for unifyvcf-0.2.3-cp311-cp311-macosx_10_9_x86_64.whl
unifyvcf-0.2.3-cp310-cp310-win_amd64.whl CPython 3.10 CPython 3.10 Windows x86-64 Details for unifyvcf-0.2.3-cp310-cp310-win_amd64.whl
unifyvcf-0.2.3-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.3-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
unifyvcf-0.2.3-cp310-cp310-macosx_10_9_x86_64.whl CPython 3.10 CPython 3.10 macOS 10.9+ x86-64 Details for unifyvcf-0.2.3-cp310-cp310-macosx_10_9_x86_64.whl
unifyvcf-0.2.3-cp39-cp39-win_amd64.whl CPython 3.9 CPython 3.9 Windows x86-64 Details for unifyvcf-0.2.3-cp39-cp39-win_amd64.whl
unifyvcf-0.2.3-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.17+ x86-64, Linux glibc 2.28+ x86-64 Details for unifyvcf-0.2.3-cp39-cp39-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
unifyvcf-0.2.3-cp39-cp39-macosx_10_9_x86_64.whl CPython 3.9 CPython 3.9 macOS 10.9+ x86-64 Details for unifyvcf-0.2.3-cp39-cp39-macosx_10_9_x86_64.whl

Total release size: 15.6 MB

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

Download URL unifyvcf-0.2.3-cp314-cp314-win_amd64.whl
Size 277.7 kB
Tags CPython 3.14 Windows x86-64
SHA-256 checksum
How to use checksums
4df8221c864cff670b2c22b23b9211e2c736cd08823fd64d33916c97c9a35bf6
BLAKE2b-256 checksum
How to use checksums
08c7a263c7d93e5080ced8ce86c806bb522af74a7b1593462a62586b9778d44e
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.3-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL unifyvcf-0.2.3-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 2.0 MB
Tags CPython 3.14 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
d3ba7f9429f73e7c48f027a8632958d9d818c6c0baf833da9cae4468e52260b3
BLAKE2b-256 checksum
How to use checksums
7a39c262112c1b3af17b43359464015e7405fd3a23b5eff4718c0e1e680feab2
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.3-cp314-cp314-macosx_10_15_x86_64.whl

Download URL unifyvcf-0.2.3-cp314-cp314-macosx_10_15_x86_64.whl
Size 321.4 kB
Tags CPython 3.14 macOS 10.15+ x86-64
SHA-256 checksum
How to use checksums
38176045838b9e69434ffb63ec66412e9dbc78c15bd975e2cef0c218941b37a7
BLAKE2b-256 checksum
How to use checksums
d067cf701e559d1a2151d413c2581122fcbd8c373a5671ea531901848f5a2833
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.3-cp313-cp313-win_amd64.whl

Download URL unifyvcf-0.2.3-cp313-cp313-win_amd64.whl
Size 273.6 kB
Tags CPython 3.13 Windows x86-64
SHA-256 checksum
How to use checksums
68f04b237228a67568cf1fdf8f833fe80ded0ddacf9383d82406dffd38aedb01
BLAKE2b-256 checksum
How to use checksums
70cad30cfdd0081aab0779629afb03b3912fe060cfec6b65d16353c2dd6fb89f
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.3-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL unifyvcf-0.2.3-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 2.0 MB
Tags CPython 3.13 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
cee765051d766cadb28cb469a4d272a18823d3f6cbfb996c8fd0cdd1636bbb6a
BLAKE2b-256 checksum
How to use checksums
cc53c6449c4715d7844759c04ae448bda311acb638ad34a0bfec1f9cc51cad61
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.3-cp313-cp313-macosx_10_13_x86_64.whl

Download URL unifyvcf-0.2.3-cp313-cp313-macosx_10_13_x86_64.whl
Size 322.0 kB
Tags CPython 3.13 macOS 10.13+ x86-64
SHA-256 checksum
How to use checksums
e8abf802aca12cf5ba38b6c3ff47528c58aee351fd4e07a4f98c554c3046a2df
BLAKE2b-256 checksum
How to use checksums
0b2680092709b3f5261013f84e6df23c697f13ac91bec14ad25caeca0a6b77fe
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.3-cp312-cp312-win_amd64.whl

Download URL unifyvcf-0.2.3-cp312-cp312-win_amd64.whl
Size 275.5 kB
Tags CPython 3.12 Windows x86-64
SHA-256 checksum
How to use checksums
37cd5823752a83b3f9d51e9d091a220e26faca4408edb3da3335a4304c5c8945
BLAKE2b-256 checksum
How to use checksums
b0af00ab66e66d780b29d7100ddbbc915144a2a9b2765fc7c90ff481ae944d26
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.3-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL unifyvcf-0.2.3-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 2.0 MB
Tags CPython 3.12 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
da31586bec057573f61330e58114c4e856106e975e3f7bbfdb187e29267a3a05
BLAKE2b-256 checksum
How to use checksums
2f812eb2b849cc83e8956c2687c18a3a341d44ef944a5aedb5f47ae0d52e8690
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.3-cp312-cp312-macosx_10_13_x86_64.whl

Download URL unifyvcf-0.2.3-cp312-cp312-macosx_10_13_x86_64.whl
Size 323.3 kB
Tags CPython 3.12 macOS 10.13+ x86-64
SHA-256 checksum
How to use checksums
c1f5df9990273328336583c3aead3b5282983b1a1bb1daac05f72d05df907110
BLAKE2b-256 checksum
How to use checksums
f4afb6dbf2dee6f05bc63ccd7010ed12efc4a8b2429fe0747f05364c4304ed89
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.3-cp311-cp311-win_amd64.whl

Download URL unifyvcf-0.2.3-cp311-cp311-win_amd64.whl
Size 283.7 kB
Tags CPython 3.11 Windows x86-64
SHA-256 checksum
How to use checksums
514061058aa10c28666ff7779e32a212e72c784e2d08e4e71b941f5e6884a362
BLAKE2b-256 checksum
How to use checksums
adab79e1fefbfb5deb7dbd20a12def450830832b6d1530cb21dee2132edc5d1c
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.3-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL unifyvcf-0.2.3-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 2.0 MB
Tags CPython 3.11 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
7cdebb1ffa433df8819ee146db9ffc8ca0781a3c23cd3327de87575f439ecc9a
BLAKE2b-256 checksum
How to use checksums
eabd4db8678130ade0203110773f73052ca9ffdd42ea10688cdd31a67f4fb268
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.3-cp311-cp311-macosx_10_9_x86_64.whl

Download URL unifyvcf-0.2.3-cp311-cp311-macosx_10_9_x86_64.whl
Size 318.5 kB
Tags CPython 3.11 macOS 10.9+ x86-64
SHA-256 checksum
How to use checksums
ab818351e0e17a6988dd873e5a9d98ae7c2dde82c1005f6be4de4a8617b23ff0
BLAKE2b-256 checksum
How to use checksums
3a93abdbb18888dbc9f8134f9b01366f53aa40fa232e5c87d8724645000fca2d
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.3-cp310-cp310-win_amd64.whl

Download URL unifyvcf-0.2.3-cp310-cp310-win_amd64.whl
Size 284.7 kB
Tags CPython 3.10 Windows x86-64
SHA-256 checksum
How to use checksums
5f9183d5cd94b7f00b39ec525f79fc8fbd3a7a069b4887b6e6c59b4bb0043eac
BLAKE2b-256 checksum
How to use checksums
f4e6f450d0559b782d6399c5900399472ddf8092507485f9772516a1b391ba7f
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.3-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL unifyvcf-0.2.3-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 2.0 MB
Tags CPython 3.10 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
77a5ab866a7de4b7e1eda85dda19dd3e351aa41b66ed02032976821bd92229d5
BLAKE2b-256 checksum
How to use checksums
83e18ca10a78d3a886951076bf12ac795aa34f7327d3d4a349e57909904f6dfb
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.3-cp310-cp310-macosx_10_9_x86_64.whl

Download URL unifyvcf-0.2.3-cp310-cp310-macosx_10_9_x86_64.whl
Size 323.7 kB
Tags CPython 3.10 macOS 10.9+ x86-64
SHA-256 checksum
How to use checksums
98eed41cfca174bbaf0b7d8d7722b0a058a7712213b85b83272ad36e382b34d2
BLAKE2b-256 checksum
How to use checksums
357873e6c801b3bf7aaf9e3a2307b4a422b6dd838a458707fd8971b600ee99a0
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.3-cp39-cp39-win_amd64.whl

Download URL unifyvcf-0.2.3-cp39-cp39-win_amd64.whl
Size 285.8 kB
Tags CPython 3.9 Windows x86-64
SHA-256 checksum
How to use checksums
09a0ef688a43e42750749479a030535f51b4b98ac0fdde8faeb1ae0254fcf439
BLAKE2b-256 checksum
How to use checksums
08b4b706d6386741900f4d2a91f5a48181ceec324e0bfa3342de5277a260a1f2
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.3-cp39-cp39-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL unifyvcf-0.2.3-cp39-cp39-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 2.0 MB
Tags CPython 3.9 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
fbdd0a1e201d6c41c1d3e9c2aa168e3558dbee9d4c084e797df0e54671d72ce7
BLAKE2b-256 checksum
How to use checksums
3f2679fdbb0929ca81b6618bf5ffe31eab7f0a05e2082637c8bbb622484204cc
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.3-cp39-cp39-macosx_10_9_x86_64.whl

Download URL unifyvcf-0.2.3-cp39-cp39-macosx_10_9_x86_64.whl
Size 326.2 kB
Tags CPython 3.9 macOS 10.9+ x86-64
SHA-256 checksum
How to use checksums
3aed129120ed4a64b4db69952ea1284c114d22e19cd5b2639439b5df4990ca0a
BLAKE2b-256 checksum
How to use checksums
c253965d66a5436b1b229510e58f84246051e655dfb929bad5eb6f7f257a0b32
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.3

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