GeneyxPgxParser
Converts pharmacogenomics caller output — PharmCAT, pbStarPhase, PyPGx, the ONT PGx workflow, a Thermo Fisher PharmacoScan report, or a plain Gene/Diplotype table — into the JSON format Geneyx Analysis consumes for PGx reporting.
Install it next to your own PacBio, ONT or array pipeline, run it on the output, and upload the result to Geneyx.
pip install GeneyxPgxParser
geneyx-pgx-parser HG002.pharmcat.report.json HG002.pbstarphase.json --output-json HG002.geneyx-pgx-results.json
Output format
A JSON array, one entry per gene - every gene the input files call, nothing dropped - with each value as the vendor file writes it:
[
{
"Id": "CYP2D6",
"Name": "CYP2D6",
"StarAllele": "*1/*3",
"Activity": "Intermediate Metabolizer",
"ActivityScore": "1.0",
"HaplotypeAlleles": null
},
{
"Id": "IFNL3",
"Name": "IFNL3",
"StarAllele": "Reference/rs12979860",
"Activity": "Unfavorable Response",
"ActivityScore": null,
"HaplotypeAlleles": [
["Reference"],
["rs12979860", "rs8099917", "rs12980275"]
]
},
{
"Id": "HLA-DRB1",
"Name": "HLA-DRB1",
"StarAllele": "*04:01:01:10/*07:01:01:01",
"Activity": null,
"ActivityScore": null,
"HaplotypeAlleles": null
}
]
The parser does not translate. Since 0.2.0 mapping vendor terms to Geneyx
terms is done on the report side: StarAllele and Activity are the vendor's
own diplotype and phenotype, unchanged - PharmVar sub-alleles (*2.001/*4.015),
every HLA field, Thermo's tokens (rs2231142G/rs2231142G) and phenotype codes
(IM, IM_or_PM), PharmCAT's terms (ivacaftor non-responsive in CF patients),
no-call words (./., Unknown/Unknown) and the caller's allele order included.
Id/Name— the gene symbol. Both are required; the Geneyx report keys its result set onIdand filters onName.StarAllele— the diplotype exactly as the caller wrote it, ornullwhen the file names the gene without a call (an empty cell).Activity— the phenotype exactly as the caller wrote it (several, as PharmCAT lists for HLA-B,;-joined), ornullwhen it gave none. The one phenotype the parser looks up itself is for a caller that runs no phenotyper (PharmCAT's matcher alone, the ONT CYP2D6 report): CPIC's diplotype table, the table PharmCAT's own phenotyper reads (see ONT PGx output).ActivityScore— the vendor's activity score as it writes it (PharmCAT'sactivityScore, or CPIC's table beside a looked-up phenotype), ornull. The phenotype alone cannot always carry it: DPYD scores 0.0 and 0.5 are bothPoor Metabolizerand get different DPWG advice.HaplotypeAlleles— every allele the caller found on each of the two haplotypes, in the caller's order, ornull. Only PyPGx lists them (Haplotype1/Haplotype2); itsGenotypenames each haplotype by one allele only, the first in its allele table, so in the IFNL3 example above rs8099917 and rs12980275 were called but appear nowhere else. The lists are in PyPGx's phase order, which need not beStarAllele's order, and hold every allele whose definition the haplotype matches, so an allele that another contains appears beside it (*1with*17). A gene PyPGx calls from copy number alone (GSTT1, UGT2B17) has empty haplotype cells andnull.
These names are matched case-sensitively on the Geneyx side. Do not rename them.
ActivityScore and HaplotypeAlleles are additions the Geneyx side does not
read yet; its JSON reader skips members it does not know, so they are safe to
carry. 0.2.0 removed UnsupportedAlleles from the array and inReport /
reportNote / vendorDiplotype from the provenance: they described the check
against the report's dataset, which belongs to the report now.
A second file, <output>.provenance.json, is written alongside the result. It
records the caller versions, the table versions read, and per-gene warnings.
It is not part of the upload contract — it exists so a report can be traced
back to what produced it. Each gene carries source (the caller its call came
from), phenotypeSource (CPIC / DPWG / PharmCAT / Thermo, or CPIC for a
looked-up phenotype) and coverageCaveats: what the caller could not see for
it, which the reported call does not rule out - PharmCAT's
Missing_Positions / Uncallable_Haplotypes (the matcher TSV) and
uncalledHaplotypes / variants without a call (the JSON), Thermo's
Unknown Call alternatives (GAN-9404). For NA19207 that is CYP2C9 *6/*25/*85,
G6PD (9 variants), NUDT15 *6/*9/*18, DPYD *3/*7 and RYR1. The result is
unchanged by them. The sidecar's top level has samples, the sample each
input file names (PharmCAT's title, the matcher TSV's Sample column, the
ONT CYP2D6 report's Sample row, PyPGx's first column, Thermo's CEL file),
warnings for the run (a sample-ID mismatch between the files, or between a
file and the sample its name is for: NA19207's matcher TSV says 7NA19207),
and cpicMisses, the matcher/ONT diplotypes CPIC's table had no phenotype for.
A PyPGx gene also carries phaseExtended: true when a called allele has
every defining variant absent from the 1KGP panel PyPGx phases with, so Beagle
dropped them and PyPGx placed the allele by its phase-extension heuristic
(pypgx_panel_gaps.json, a measured list per PyPGx release); false for any
other PyPGx call; null for a caller whose phase is not PyPGx's. The result
is unchanged by it.
Supported inputs
| Input | Detected by | Provides |
|---|---|---|
*.pharmcat.report.json |
name or pharmcatVersion |
diplotypes, phenotypes, tool + data versions (PharmCAT 2.x and 3.x) |
*.pharmcat.phenotype.json |
name or geneReports |
diplotypes, phenotypes |
*.pbstarphase.json |
name or gene_details |
diplotypes only; alone (PacBio WDL v4) the primary caller |
*.pbstarphase.tsv |
.tsv header |
as the JSON (PacBio v4 summary) |
<GENE>.tsv (PyPGx) |
.tsv header |
diplotype + phenotype, one gene per file |
*.pharmcat.tsv (ONT) |
.tsv header |
diplotypes only (PharmCAT matcher; no CYP2D6) |
CYP2D6/report.tsv (ONT) |
Sample first row |
CYP2D6 diplotype only |
*_phenotype.rpt (Thermo) |
.rpt or Known Call |
diplotype + phenotype (PharmacoScan plate report; --sample) |
*.csv / *.json table |
fallback | Gene + Diplotype (+ optional Phenotype) |
The minimal table is the upload format: a header with Gene and Diplotype
is enough. Column names are matched loosely (gene, geneSymbol, symbol;
diplotype, genotype, starAllele).
Why two files are better than one
PharmCAT only reports genes that have a CPIC or DPWG guideline. In a PacBio HG002 run, pbStarPhase called 35 genes and PharmCAT reported 22. Passing the pbStarPhase summary alongside the PharmCAT output adds the other 13 — NAT2, CYP1A2, CYP2A13, CYP2C8 and the HLA genes beyond HLA-A/B — with pbStarPhase's diplotype and no phenotype (pbStarPhase writes none).
Where both files describe the same gene, PharmCAT wins: its call comes with PharmCAT's phenotype and activity score.
pbStarPhase on its own (PacBio WDL v4)
The HiFi human WGS WDL v4 dropped PharmCAT, so a v4 run has only the
pbStarPhase output. Then pbStarPhase is the primary caller: every gene it
calls is reported, as pbStarPhase wrote it, with Activity: null - the file
carries no phenotype, and since 0.2.0 the parser derives none (up to 0.1.8 it
ran PyPGx's phenotype step on the diplotype). Up to 0.1.5 the parser treated
pbStarPhase as PharmCAT's supplement even when it came alone, and a v4 sample
came out with 4 genes.
ONT PGx output
The ONT PGx workflow writes its calls to two files, and both are needed:
<sample>.pharmcat.tsv holds every gene except CYP2D6, and
CYP2D6/report.tsv holds CYP2D6. Pass both, and they merge into one array:
geneyx-pgx-parser NA19207.pharmcat.tsv NA19207/CYP2D6/report.tsv --output-json NA19207.geneyx-pgx-results.json
The workflow runs only PharmCAT's allele matcher, not its phenotyper, so
neither file carries a phenotype. The Activity is looked up in CPIC's own
diplotype table - the table PharmCAT's phenotyper reads - packaged as
Mappings/cpic_diplotypes.json. The lookup tries both allele orders, writes
three or more copies the way CPIC does (*2x3 -> *2x≥3), and falls back to
the haplotype columns where the matcher TSV abbreviates (CFTR); only the
lookup tries these spellings, StarAllele stays as the caller wrote it. CPIC's
phenotype is the Activity and its activity score the ActivityScore; which
CPIC key answered goes in the provenance sidecar.
DPYD is usually unphased: PharmCAT lists the variants it found rather than a
diplotype, and they are reported as-is, ;-separated
(c.85T>C (*9A);c.557A>G). Two variants can only be one on each strand, so
the pair is looked up as a diplotype (the StarAllele keeps the ;); three
or more need CPIC's lowest-two rule and are left without an Activity rather
than guessed.
Genes the table cannot answer keep Activity: null: CYP3A4 and CYP4F2 have
no CPIC diplotype table, G6PD needs the sample's sex, and IFNL3 / VKORC1 have
no CPIC diplotype table either.
--input-dir does not descend into CYP2D6/, so name the report explicitly.
Keeping the CPIC table current
CPIC revises its tables in place - SLCO1B1 *41 went from uncertain to no
function on 2025-09-23, so NA19207's *37/*41 is Decreased Function here but
Indeterminate from PharmCAT 2.15.5, whose data predates the change.
The table is kept current in pgx-metadata, where
Test_CpicLiveTable.py fetches CPIC and fails while the table disagrees
with it, listing every changed, added and removed diplotype and every
changed phenotype term. The refreshed table reaches this package as a new
mapping bundle.
Running PharmCAT's phenotyper instead
The same Activity can come from running the rest of PharmCAT on the
workflow's <sample>.match.json, with the CYP2D6 call handed back to it as an
outside call. Use the same PharmCAT version as the workflow (wf-pgx v0.1.7
ships 2.15.5):
geneyx-pgx-parser NA19207/CYP2D6/report.tsv --pharmcat-outside-call NA19207.outside.tsv
pharmcat -phenotyper -pi NA19207.match.json -po NA19207.outside.tsv -reporter -reporterJson -o out -bf NA19207
geneyx-pgx-parser out/NA19207.report.json --output-json NA19207.geneyx-pgx-results.json
The report.json is the same file the PacBio path produces, and PharmCAT's
phenotypes are used as-is - no CPIC lookup. Unphased DPYD keeps its
;-separated variants as StarAllele and takes the phenotype PharmCAT gives
the pair.
Thermo Fisher PharmacoScan
Axiom Analysis Suite's apt-pgx-translation writes one *_phenotype.rpt per
plate, so the file holds every sample on it while the Geneyx result is per
sample. Name the sample, by CEL file name or its stem:
geneyx-pgx-parser 2026-02-18-PharmacoScan24F_phenotype.rpt --sample HG03225 --output-json HG03225.geneyx-pgx-results.json
A file with one sample needs no --sample; a file with several and no choice
is refused with the list of samples it holds (GAN-8867).
What the parser does with the report:
Known Callis theStarAlleleandPhenotype CalltheActivity, both exactly as Thermo writes them (rs2231142G/rs2231142GandNF,Met/ValBandIM_or_PM,*1/*29andNM). Thermo's allele vocabulary, its phenotype codes, a,-separatedKnown Call(Thermo could not phase the sample:*1/*14,*4/*37) and a copy-number gain ((*1/*10)xN) are the report's to read. Up to 0.1.8 the parser translated the tokens throughthermo_alleles.jsonand replacedPhenotype Callwith PyPGx's phenotype.- Rows with no
Known Call(UNDH,CN_HybridLoss) are written as no-calls (StarAllele: null), with the interpretation code and theUnknown Callcandidates in the provenance. Unknown Callbeside aKnown Callis a coverage caveat. Control1's CYP2D6*1/*29stays*1/*29NM; Thermo's alternatives with a haplotype the chip cannot resolve (*2/UNK,*34/UNK,...) go to the sidecar'scoverageCaveatsfor the gene, and weigh nothing (GAN-9404).- An interpretation code that qualifies the call (
CN_HybridGainon*2/*4,CN_Gain,CN_Error) keeps the call as written and adds a warning saying what the code means;CN_NoCall(no copy number reported) adds a coverage caveat. - Every gene the chip calls is reported (ALDH2, FMO3, TNF, UGT1A9 …). Only
CYP2CRS12777823is left out: it is a carrier for the rs12777823 warfarin variant rather than a gene (ignored_genesinthermo_alleles.json, whosegene_aliasesalso giveMTRNR1its gene symbolMT-RNR1). On the 24F panel that is 31 of the 32 reported genes.
A report records its own library as thermoLibrary in the provenance sidecar
(read from its #%MetabolizerFile= header); one made with a different library
than thermo_alleles.json names carries a warning on every gene.
Merging rules
- One entry per gene. PharmCAT 2.x emits a gene report per phenotype source, so the same 22 genes appear under both CPIC and DPWG. One source is preferred and the other is consulted only as a fallback — see below.
- One caller per gene. Where several files call a gene, the higher-ranked caller wins (PharmCAT's report over its phenotype JSON over pbStarPhase / PyPGx / ONT), and its diplotype, phenotype and activity score are reported together: one caller's phenotype is never attached to another's diplotype.
- No translation.
StarAlleleandActivityare the winning caller's own values (see Output format); only PyPGx's trailing;on a cell is dropped. Several candidate diplotypes (pbStarPhase's list, PharmCAT's unphased DPYD variants) are reported;-separated, never the first alone. - A no-call is written, never dropped. A gene the caller names but did not
call is written with the caller's own word (
./.,Unknown/Unknown,Indeterminate) as itsStarAllele, ornullfor an empty cell, and no Activity. Where the preferred caller made no call and another caller in the run did, the other call is reported, with a warning saying so. - A placeholder is not a phenotype. PharmCAT's
n/a(ano_call_tokensvalue ingene_rules.json) isActivity: null. PyPGx's own values,Indeterminateand an empty cell included, are reported as PyPGx wrote them.
Choosing a phenotype source
PharmCAT phenotypes come from two guideline bodies, CPIC and DPWG, and they do not always agree. Pick one:
geneyx-pgx-parser HG002.pharmcat.report.json --phenotype-source DPWG
The default is CPIC (the first entry of phenotype_source_preference in
gene_rules.json). The choice only reorders the sources — it never narrows the
output. When the chosen source has no usable phenotype for a gene, the next
source in the default order is used instead, and the substitution is recorded:
{
"Id": "CYP2B6",
"phenotypeSource": "CPIC",
"warnings": ["no phenotype from DPWG; taken from CPIC"]
}
"No phenotype" covers two cases: the source reported none at all (HG002
CPIC: CYP3A4, CYP4F2, VKORC1) or it reported a placeholder such as n/a
(HG002 DPWG: CYP2B6). The other source's phenotype and activity score are
taken only for the same diplotype, as that source wrote them - a DPWG term
(-1639 GG for VKORC1) is reported as DPWG writes it.
The source selection affects Activity and ActivityScore only — StarAllele
is identical either way, since both sources describe the same call. The preference actually used is
written to the provenance file as phenotypeSourcePreference.
PyPGx
The Geneyx PyPgx pipeline has produced this JSON format since it shipped, by
reading PyPGx's per-gene data.tsv and writing its Genotype and Phenotype
columns straight through. This parser does the same, as it now does for every
caller.
Each PyPGx file covers one gene, and the gene comes from the file name
(CYP2C19.tsv), because PyPGx's own table has no gene column. A table still
named data.tsv needs a Gene column, or parsing fails rather than reporting
a gene called "data". Point the parser at the whole results folder:
geneyx-pgx-parser --input-dir /path/to/pgx/results --output-json sample.geneyx-pgx-results.json --gzip
Mapping tables
The clinical vocabulary lives in GeneyxPgxParser/Mappings/ as versioned JSON.
The tables are owned by pgx-metadata (Azure DevOps), where reference
sources are snapshotted, mapping proposals are reviewed and approved, and a
signed, versioned mapping bundle is built. This repository pins one bundle
in bundle.lock; the packaged tables are exactly that bundle's, and
Test_MappingBundle.py fails if a table is edited here. To adopt a new bundle:
python scripts/sync_bundle.py --from <pgx-metadata bundle folder> --public-key bundle.pub
and open one pull request with bundle.lock and the tables it changed.
pgx-metadata runs the parser against its candidate tables by naming their
folder in GENEYX_PGX_MAPPINGS_DIR; unset, the packaged tables are used.
| File | Read for |
|---|---|
gene_rules.json |
phenotype source preference, gene scope, no-call tokens, CPIC-lookup callers |
cpic_diplotypes.json |
the phenotype and activity score of a matcher / ONT call |
thermo_alleles.json |
Thermo gene aliases, ignored pseudo-genes and the library it was built for |
pypgx_panel_gaps.json |
phaseExtended in the provenance |
The bundle still carries the term tables (phenotype_terms.json,
genotype_terms.json, allele_terms.json, pypgx_phenotypes.json,
report_diplotypes.json, and the allele and phenotype-code halves of
thermo_alleles.json); since 0.2.0 the parser does not read them. Mapping
vendor terms to Geneyx terms is the report side's job, and that is where
those tables belong.
Development
pip install -e .
pytest GeneyxPgxParser/Test/Test_GeneyxPgxParser.py -v
pip install -e . compiles the modules in place, and Python loads a
.pyd/.so in preference to the .py beside it — so after an edit the tests
keep running the copy built at install time until you reinstall. The
symptom is a change that provably has no effect. Delete the build artefacts to
go back to running the sources:
find GeneyxPgxParser -name "*.pyd" -delete -o -name "*.so" -delete -o -name "*.c" -delete
They are gitignored, and CI builds the wheels from source regardless.
Test fixtures are real PacBio output for HG002, a public GIAB reference sample, ONT output for NA19207, and Thermo's own PharmacoScan 24F demo plate unmodified — 24 samples × 32 genes, two Thermo controls and 22 1000 Genomes / Coriell cell lines, as shipped with Axiom Analysis Suite. The whole plate is kept rather than a cut-down copy because its awkward calls are spread across samples: between them they cover every interpretation code the format has. No patient data belongs in this repository.
Metadata
Release files for GeneyxPgxParser 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
Total release size: 50.3 MB
Release files / geneyxpgxparser-0.2.0-cp314-cp314-win_amd64.whl
| Download URL | geneyxpgxparser-0.2.0-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
ac7a660dac26668c47422170b2d6f36945db06610e0950d7e8be173261ee077f
|
|
BLAKE2b-256 checksum How to use checksums |
48f946e14cdde8840dbedf03d3497731c76594c6c61dd17d0962737779ebe198
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.18
|
Release files / geneyxpgxparser-0.2.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | geneyxpgxparser-0.2.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 5.4 MB |
| Tags | CPython 3.14 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
a0293ac291957ed07b0405da249ea9e8357342f900bd1be6559ce55c33be1884
|
|
BLAKE2b-256 checksum How to use checksums |
9c72cdb31e14b0b63e07b0d02bcd5d6251421002f9ce159a9a6c2534083f271d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.18
|
Release files / geneyxpgxparser-0.2.0-cp314-cp314-macosx_10_15_x86_64.whl
| Download URL | geneyxpgxparser-0.2.0-cp314-cp314-macosx_10_15_x86_64.whl |
|---|---|
| Size | 1.5 MB |
| Tags | CPython 3.14 macOS 10.15+ x86-64 |
|
SHA-256 checksum How to use checksums |
d90ccf6fd11d4fb1914b5183eff9ae16e6573bce82ea147fda000ddbf6011bcf
|
|
BLAKE2b-256 checksum How to use checksums |
2189caac8ac2cac3fe96b57615a4b28de48226504b93a74fdc2d65031323cd2b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.18
|
Release files / geneyxpgxparser-0.2.0-cp313-cp313-win_amd64.whl
| Download URL | geneyxpgxparser-0.2.0-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
94b795b7a9a97e7dbf6ca1a0d954123f7d2dcb53f520d93d45c6e9ffcf2ce29f
|
|
BLAKE2b-256 checksum How to use checksums |
e1594ec379c6ccf0b074e8424328d4bc16bb8651c877aedd2820efbdc756aa95
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.18
|
Release files / geneyxpgxparser-0.2.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | geneyxpgxparser-0.2.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 5.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 |
28e162cf52a9eaf9141e744a69d8e1b04f8052655f7163be8c4e1e0dcbcb878c
|
|
BLAKE2b-256 checksum How to use checksums |
63fa64c1da9acb55ff7346fd270035098cf77160ce20afcb581df6cc8573a809
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.18
|
Release files / geneyxpgxparser-0.2.0-cp313-cp313-macosx_10_13_x86_64.whl
| Download URL | geneyxpgxparser-0.2.0-cp313-cp313-macosx_10_13_x86_64.whl |
|---|---|
| Size | 1.5 MB |
| Tags | CPython 3.13 macOS 10.13+ x86-64 |
|
SHA-256 checksum How to use checksums |
36be5ea1e6b026f7d9b7e5597db7c694fec3c5c1e87dce3f514dbc0093f7ce95
|
|
BLAKE2b-256 checksum How to use checksums |
8a99ecddd78824362d84e319ee00db2e2a404413e825a3dbbad85376b97b9a02
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.18
|
Release files / geneyxpgxparser-0.2.0-cp312-cp312-win_amd64.whl
| Download URL | geneyxpgxparser-0.2.0-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
be904d98e6c0a8312e81e1c0e2522b79ecd56084c2cc6c4be4d7a070b9b37cee
|
|
BLAKE2b-256 checksum How to use checksums |
78ef96e8fe676ceb89a86d0f33693eed73f18a8cd6ce8d1efc36a197c80e220c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.18
|
Release files / geneyxpgxparser-0.2.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | geneyxpgxparser-0.2.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 5.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 |
2273814eb181aefa84ada413e0fb912b21d2f6743ae441c195550e191cde04eb
|
|
BLAKE2b-256 checksum How to use checksums |
1ca56b55aa3c3257e578e4da1da7f7844f6d0128a2f77940607843ba8d8ca2c2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.18
|
Release files / geneyxpgxparser-0.2.0-cp312-cp312-macosx_10_13_x86_64.whl
| Download URL | geneyxpgxparser-0.2.0-cp312-cp312-macosx_10_13_x86_64.whl |
|---|---|
| Size | 1.5 MB |
| Tags | CPython 3.12 macOS 10.13+ x86-64 |
|
SHA-256 checksum How to use checksums |
d95f99bd17e6fbe548349036d1959780e25ed1b6e2b9f4b3f198136a57b340dd
|
|
BLAKE2b-256 checksum How to use checksums |
4043a059db0d88d486788dfeb7df90085993eb59c3aad3622971af74a36b0591
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.18
|
Release files / geneyxpgxparser-0.2.0-cp311-cp311-win_amd64.whl
| Download URL | geneyxpgxparser-0.2.0-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
5725249228954f22c473b38436d8c09d6ce06ec119dde3d8758fc539c4af6bc7
|
|
BLAKE2b-256 checksum How to use checksums |
7dcba34066d2b69e1918483362576f99e3a719da905e3f4ee9ebfdfe133473a9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.18
|
Release files / geneyxpgxparser-0.2.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | geneyxpgxparser-0.2.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 5.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 |
0bc336558c9b682977d8c7bc4c7efcfaa0ba0db41fd8e63993d8fdbfd8b82ba8
|
|
BLAKE2b-256 checksum How to use checksums |
375e19015018784da95c339d62e0ef082af37ae5d123a53deaab6c465908733d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.18
|
Release files / geneyxpgxparser-0.2.0-cp311-cp311-macosx_10_9_x86_64.whl
| Download URL | geneyxpgxparser-0.2.0-cp311-cp311-macosx_10_9_x86_64.whl |
|---|---|
| Size | 1.5 MB |
| Tags | CPython 3.11 macOS 10.9+ x86-64 |
|
SHA-256 checksum How to use checksums |
7aa9d5f3b530fa1d307459d2f82c3863671109417ffb40f1438afc87abbb4b33
|
|
BLAKE2b-256 checksum How to use checksums |
f2c1b692802df311bae953d2b3b6c9da84daf9d36ccf635ef716be6b61f63357
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.18
|
Release files / geneyxpgxparser-0.2.0-cp310-cp310-win_amd64.whl
| Download URL | geneyxpgxparser-0.2.0-cp310-cp310-win_amd64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.10 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
4ef8b8ea2ddce498dadc0e47d1c0c7107f076c77cc012f27264a74992e395d4b
|
|
BLAKE2b-256 checksum How to use checksums |
e2be7629530e83452b960548e81934e9233f538c89dc100b7ed9a2b19af90325
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.18
|
Release files / geneyxpgxparser-0.2.0-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | geneyxpgxparser-0.2.0-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 5.3 MB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
550d8bc0f4dc5f0109274396ccb09f56c428d767eb5179100798f88ba1e8df92
|
|
BLAKE2b-256 checksum How to use checksums |
1afa2a229ed1a474afed6570afec1ca6b4d3897527b7247f9a8c3613e6975202
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.18
|
Release files / geneyxpgxparser-0.2.0-cp310-cp310-macosx_10_9_x86_64.whl
| Download URL | geneyxpgxparser-0.2.0-cp310-cp310-macosx_10_9_x86_64.whl |
|---|---|
| Size | 1.5 MB |
| Tags | CPython 3.10 macOS 10.9+ x86-64 |
|
SHA-256 checksum How to use checksums |
a2e761ad4ba32e3969bbdb856b37efbab81cfaba056ddf61fff94c04e7f4ca77
|
|
BLAKE2b-256 checksum How to use checksums |
1d64417eec7851df5bed72a5f2dfd7ffef3713bc4782ee0a002090d41fb6a799
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.18
|
Release files / geneyxpgxparser-0.2.0-cp39-cp39-win_amd64.whl
| Download URL | geneyxpgxparser-0.2.0-cp39-cp39-win_amd64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.9 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
9b8a21fb5462e742a56544b1d5e9f12b1b5112e17b64a013e123c201c4c466d9
|
|
BLAKE2b-256 checksum How to use checksums |
291b2b536491230cfac1a88e43f6de17f1b3b470b0dc7bfb093aca9706d8450b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.18
|
Release files / geneyxpgxparser-0.2.0-cp39-cp39-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | geneyxpgxparser-0.2.0-cp39-cp39-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 5.3 MB |
| Tags | CPython 3.9 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
01c797661e35f4e61f25b425d408bef16dca162c6d7f2e92abfd7e39204eb3a6
|
|
BLAKE2b-256 checksum How to use checksums |
a4ad37ad1ac327391acf4799022fafc23618a64e6c42e59072c5bc3904ac679a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.18
|
Release files / geneyxpgxparser-0.2.0-cp39-cp39-macosx_10_9_x86_64.whl
| Download URL | geneyxpgxparser-0.2.0-cp39-cp39-macosx_10_9_x86_64.whl |
|---|---|
| Size | 1.5 MB |
| Tags | CPython 3.9 macOS 10.9+ x86-64 |
|
SHA-256 checksum How to use checksums |
90c483ca92ff9ad29d2638424452ba98303f469451cd9ae5d27a5098719b408c
|
|
BLAKE2b-256 checksum How to use checksums |
8196fc7ef255afe07444855a7c31e624bd36f98f1e07a81622e889b78f8ba55c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.18
|
Security for GeneyxPgxParser 0.2.0
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.