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:
[
{
"Id": "CYP2C19",
"Name": "CYP2C19",
"StarAllele": "*1/*1",
"Activity": "Normal Metabolizer",
"InReport": true,
"ReportNote": null
},
{
"Id": "HLA-DRB1",
"Name": "HLA-DRB1",
"StarAllele": "*04:01/*07:01",
"Activity": null,
"InReport": false,
"ReportNote": "HLA-DRB1 is not a gene of report dataset v2.9.0-PGX-Data-90genes-2026-10-11"
}
]
Id/Name— the gene symbol. Both are required; the Geneyx report keys its result set onIdand filters onName.StarAllele— the diplotype (*1/*2), its two alleles in PyPGx's order whichever order the caller wrote them in (see Merging rules).Activity— the phenotype / metaboliser status (Normal Metabolizer), ornullwhen it is not known.InReport— whether the Geneyx PGx report will show this result:falsewhen the gene is not in the report's dataset, has no drug there, or itsStarAlleleis not one of the report's diplotypes for the gene.ReportNote— why not, whenInReportisfalse; when it istrue, the phenotype the report shows if it differs fromActivity(orActivityisnull), elsenull.
These names are matched case-sensitively on the Geneyx side. Do not rename them.
InReport and ReportNote are additions the Geneyx side does not read yet; its
JSON reader skips members it does not know, so they are safe to carry.
A second file, <output>.provenance.json, is written alongside the result. It
records the caller versions, the mapping-table versions used, per-gene warnings,
and any term that had no Geneyx mapping. It is not part of the upload contract —
it exists so a report can be traced back to what produced it. A gene's warnings
also say when the Geneyx PGx report cannot show its StarAllele (the report
looks a result up by that exact string), or shows a different phenotype for 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; alone (PacBio WDL v4), the primary caller with PyPGx phenotypes |
*.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 a diplotype and
no phenotype; InReport says which of them the report can show.
Where both files describe the same gene, PharmCAT wins: it normalises
PharmVar sub-alleles (*4.015) to the core alleles (*4) that Geneyx uses.
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, sub-alleles stripped and names put in the Geneyx (PyPGx)
vocabulary, and Activity is PyPGx's phenotype for the diplotype — what a
PyPGx run would report. On HG002 that is all 35 genes, 17 with an Activity.
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 and no Activity. With
PharmCAT in the run, PharmCAT's call wins for the genes it reports, and
pbStarPhase's phenotype is never attached to PharmCAT's diplotype.
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). Which CPIC key
answered, and its activity score, go 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; 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 are
genotype-guided as on every other path.
--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.
Test_CpicLiveTable.py fetches CPIC and fails while the packaged table
disagrees with it, so CI stops the release. It never updates the table - the
failure message lists every changed, added and removed diplotype, and every
phenotype term with no Geneyx term yet, which must be added downstream too.
The update is then made by hand: refresh with
python tools/fetch_cpic_diplotypes.py, bump the table's version, map any
new term in phenotype_terms.json, make the matching downstream change, and
update the tests that pin changed answers.
The test needs network access and is marked cpic_live; skip it offline with
pytest -m "not cpic_live".
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 the diplotype; Activity is PyPGx's phenotype for it. Thermo'sPhenotype Callis only a cross-check; see below.- Allele names are translated token by token through
thermo_alleles.json, built from the SNP-level Thermo ↔ PyPGx dictionary on GAN-8867 and the diplotypes the Geneyx model was seen to accept.WT,c.=andrs2231142GbecomeReference;*28+60+80+93becomes*80+*28; a male's G6PDNullbecomesMALE;MTRNR1 Null/m.=becomesMT-RNR1 Reference/Reference. The table names Geneyx core alleles, so a PyPGx compound such as*10+*4is written*4. - A token the table does not know is kept as written and listed in the
sidecar's
unmappedTerms. It is a genomic observation the Geneyx model does not name yet, not a vocabulary term that could pass for one: RYR1c.6178G>T, a CPIC Level A malignant-hyperthermia variant, is reported asc.6178G>T/Referencerather than vanishing intoReference/Reference. - Ambiguous phase is reported, not resolved. A
,-separatedKnown Call(*1/*14,*4/*37) is Thermo saying it could not phase the sample; the candidates are emitted;-separated, like unphased DPYD on the ONT path, and the gene is flagged in the sidecar. Candidates that name the same Geneyx diplotype (*1A/*7A,*1B/*7A+1B→*1/*7) collapse to it. - Copy-number gains are kept as
(*1/*10)xNwith a warning. Thermo does not say which haplotype is duplicated, so nothing is guessed. - Rows with no
Known Call(UNDH,CN_HybridLoss) are skipped with theUnknown Callcandidates in the log. - Every gene the chip calls is reported (ALDH2, FMO3, TNF, UGT1A9 …), with
InReportfalsewhere the Geneyx PGx report has nothing for it. OnlyCYP2CRS12777823is left out: it is a carrier for the rs12777823 warfarin variant rather than a gene (ignored_genesinthermo_alleles.json). On the 24F panel that is 31 of the 32 reported genes.
Where Activity comes from: PyPGx's phenotype step
The Geneyx report is built on PyPGx. A Thermo report has a diplotype but not
PyPGx's phenotype for it, so that step is run here: once Known Call is
translated into Geneyx (PyPGx) allele names, Activity is what PyPGx's
predict_phenotype gives that diplotype — read from
Mappings/pypgx_phenotypes.json, which is generated from the PyPGx release the
pipeline runs (tools/build_pypgx_phenotypes.py, from sources/pypgx/0.27.0).
A Thermo sample therefore reads as a PyPGx sample with the same diplotype
would:
- Diplotype genes (CYP2C19, TPMT, SLCO1B1, G6PD, CFTR, RYR1, …) take
PyPGx's diplotype table; a diplotype it does not list is
Indeterminate, as in PyPGx. - Score genes (CYP2D6, CYP2C9, DPYD) add the two alleles' activity scores
— copies multiply,
+tandems add — and take PyPGx's ranges; an allele of uncertain function isIndeterminate. - Genes PyPGx gives no phenotype (NAT1/NAT2, COMT, CYP1A2, GSTM1, VKORC1, …) get no Activity, as a PyPGx run leaves them.
- No guessing. An unresolved phase (
*1/*14;*4/*37) or an unplaced copy-number gain ((*1/*7)xN) is reported only when every possible reading gives PyPGx the same phenotype; a diplotype with an allele the Geneyx model cannot name gets none. The provenance sidecar says which and why.
Thermo's own Phenotype Call (NM, NF, MHS, …) is converted per gene
through phenotype_calls in thermo_alleles.json and only compared: where
it differs from PyPGx, the gene carries a warning naming both. They differ
often — Thermo's research-use metabolizer table is coarser than PyPGx's (CFTR
NF vs PyPGx Indeterminate, G6PD Deficient vs Deficient with CNSHA,
RYR1 Indeterminate vs Malignant Hyperthermia Susceptibility for
c.14387A>G) — which is why it is not the reported value. The reconciliation
report lists every such difference on its Thermo vs PyPGx sheet.
Worth knowing when reading the output: for the twelve panel genes whose Geneyx
model carries only an Indeterminate activity (COMT, CYP1A2, CYP2A6, CYP2C8,
CYP2E1, CYP3A4, CYP3A7, CYP4F2, GSTP1, NAT1, NAT2, UGT2B7), the report will
return Indeterminate however good the diplotype is: PyPGx has no phenotype
for them, and Thermo's own call is not used. That is a gap in the Geneyx model's activity tables,
not in this parser, and it is the same gap GAN-8867 records for GSTM1.
Checking the Thermo tables against PyPGx
tools/thermo_reconcile.py rebuilds the allele dictionary from Thermo's own
library files and checks both halves of thermo_alleles.json against the
PyPGx release the Geneyx pipeline runs (pypgx_version, currently 0.27.0):
- Alleles. Every haplotype in Thermo's translation table is reduced to its hg38 variants and matched to PyPGx's core variants by content, in the GAN-8867 categories. Indels are left-normalised against hg38 first, so the UGT1A1 TA repeat (Thermo 233,760,235, PyPGx 233,760,233) is one variant. The Geneyx name this gives each token is compared with the packaged one.
- Activity. Every diplotype in Thermo's
.metabolizerfile goes through the parser and normaliser exactly as a report does, and the Activity is compared with PyPGx's phenotype computed independently from its raw tables — a check of the generatedpypgx_phenotypes.jsonand of the phenotype step. Thermo's own call against PyPGx is listed for information.
python tools/thermo_reconcile.py --report thermo_reconciliation.xlsx --check
It writes an xlsx for review (findings first, then the full dictionary and
every metabolizer row). A difference is either reviewed (accepted, with a
reason, under reviewed in thermo_alleles.json) or open (known and
awaiting review, in tools/thermo_open_findings.json, written by
--write-open). --check and the thermo_library test fail on a difference
that is neither, or on an open one that no longer occurs. Run it on every new
Thermo library, PyPGx upgrade, or change to thermo_alleles.json.
Reference files
Every input the check reads is kept, unmodified and versioned, under
sources/ — outside the package, so none of it ships in the wheel:
| Folder | What |
|---|---|
sources/thermo/<library>/ |
Thermo's *.translation(.xlsx) and *.metabolizer |
sources/pypgx/<version>/ |
PyPGx's pypgx/api/data tables at that tag |
sources/hg38/ucsc_windows.json |
hg38 windows around the indels being normalised (UCSC API) |
Each folder has a SOURCE.json with its origin and the sha256 of every file;
the tests verify them, and .gitattributes keeps the files byte-exact on
checkout. thermo_alleles.json names the versions it is built and checked
for — thermo_library (PharmacoScan_24F.r10_1) and pypgx_version — and a
report records its own library as thermoLibrary in the provenance sidecar
(read from its #%MetabolizerFile= header). A report made with a different
library is still translated, with a warning on every gene.
To bring in a new Thermo library (say r11):
- Put its two files in
sources/thermo/PharmacoScan_24F.r11/and runpython tools/thermo_reconcile.py --add-source sources/thermo/PharmacoScan_24F.r11, then fill in where they came from in theSOURCE.jsonit writes. python tools/thermo_reconcile.py --library PharmacoScan_24F.r11 --report r11.xlsxshows what the new library changes against the current table.- Update
thermo_alleles.jsonand itsthermo_library, review, then--write-open. The old library's folder stays as the record of what the earlier table versions were built from.
A new PyPGx version only needs pypgx_version changed: the tool downloads its
tables into sources/pypgx/<version>/ with their SOURCE.json.
Merging rules
- One entry per gene. PharmCAT 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 vocabulary for every caller. The report shows
StarAlleleandActivityverbatim and the PyPGx pipeline writes PyPGx's own names, so every caller's output is held to PyPGx's allele names and phenotypes: an Activity outside its gene's PyPGx phenotypes is not reported (PharmCAT's DPWGNormal Metabolizerfor CYP3A4), PharmCAT's ABCG2rs2231142 reference (G)is writtenReference, and DPYD'sc.1627A>G (*5) (heterozygous)label is writtenReference/c.1627A>G (*5), as PyPGx writes them. - One spelling for every diplotype. The two alleles are written in PyPGx's
allele order, as a PyPGx run writes them:
*4/*2becomes*2/*4,c.1627A>G (*5)/ReferencebecomesReference/c.1627A>G (*5), and each candidate of an unresolved call is ordered on its own. An allele PyPGx does not define keeps the caller's order. A male's single G6PD allele is written withMALE(MALE/A- 202A_376G), and a sub-allele number is dropped before a copy number too (*3.001xN→*3xN). The phenotype is unaffected: it is looked up in either order. - Unmapped terms are dropped, not passed through. A PharmCAT phenotype with
no Geneyx equivalent yields
Activity: nullplus a warning in the provenance file, rather than an unrecognised term that looks valid to the report. - Genotype-guided genes (IFNL3, VKORC1) take their
StarAllelefrom the rewritten allele names rather than from the phenotype. - HLA alleles are truncated to two fields (
*01:01:01:01→*01:01). - Single-allele genes (MT-RNR1) are one call, written as PyPGx writes it:
Reference/Reference,m.1555A>G/m.1555A>G(PharmCAT's1555A>Gis renamed).
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 usable phenotype from DPWG; taken from CPIC"]
}
"No usable phenotype" covers three cases: the source reported none at all
(HG002 CPIC: CYP3A4, CYP4F2, VKORC1), it reported a no-call token such as
n/a (HG002 DPWG: CYP2B6), or its term has no Geneyx mapping yet (HG002 DPWG:
DPYD 2.0 (Normal Metabolizer)).
The source selection affects Activity 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, and callers whose terms are already Geneyx terms
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. Those values are the Geneyx vocabulary, so mapping
them would change clinical output rather than normalise it — phenotype_terms.json
maps none of PyPGx's G6PD, MT-RNR1 or CFTR terms, and genotype_terms.json
knows only PharmCAT's allele names for the genotype-guided genes.
PyPGx is therefore listed in gene_rules.json under passthrough_sources: its
calls skip term mapping, sub-allele stripping and HLA truncation entirely, and
the sidecar records which callers were passed through:
{ "passthroughSources": ["pypgx"] }
Removing pypgx from that list is a clinical behaviour change gated on the
GAN-8770 mapping sheet, not a refactor.
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:
| File | Contains |
|---|---|
gene_rules.json |
structural rules — source preference, passthrough callers, HLA/sub-allele handling |
phenotype_terms.json |
PharmCAT phenotype term → Geneyx Activity term |
genotype_terms.json |
allele/diplotype rewrites for genotype-guided genes |
thermo_alleles.json |
Thermo PharmacoScan allele token → Geneyx allele name, and phenotype code → CPIC term, per gene |
phenotype_terms.json is built from the approved crosswalk
(PyPGx_PharmCAT_phenotype_crosswalk 15.07.2026.xlsx, sheet
Phenotype Crosswalk (SD), linked from GAN-8770): its Rule class column
decides where a row lands, EXACT in the passthrough block and TRANSFORM in
the per-gene block.
thermo_alleles.json is generated, not hand-written: its source is the
Dictionary sheet of PGx_Thermo_PyPGx_Reconciliation_6.xlsx on GAN-8867
(SNP-content matching of every Thermo allele against PyPGx's definitions),
checked against the diplotypes the Geneyx model accepted in
PharmacoScan_diplotype_ingestion_report.xlsx. The handful of hand overrides
(CYP2C19 *1, the UGT1A1 TA-repeat tokens, G6PD Null, MT-RNR1) each carry
their reason in the file. It is marked DRAFT until it has clinical sign-off.
A
nulltarget means the crosswalk has no approved term, not that the row is outstanding work. Today that is HLA-A and HLA-B, which the sheet marksUNSUPPORTEDpending a phenotype table from clinpgx.org (GAN-8796). The genotype-guided genes ingenotype_terms.jsonare still unfilled, because their table is a different sheet. Run the parser and readunmappedTermsin the provenance file to see what your data actually hit.
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.1.6
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.8 MB
Release files / geneyxpgxparser-0.1.6-cp314-cp314-win_amd64.whl
| Download URL | geneyxpgxparser-0.1.6-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
d74979ea1d8a035ed5d37dff8e6d84da26715bd09b505386c8c12a7fa73fd560
|
|
BLAKE2b-256 checksum How to use checksums |
53d9fecd121ae92b2d238eca0b64cb305fb39a24a147ea7d0191d8e77296081a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.17
|
Release files / geneyxpgxparser-0.1.6-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | geneyxpgxparser-0.1.6-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 5.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 |
911b4fb64d8b552ba894e634aa8ea3adf35689a0b977db328672451a373ae5b6
|
|
BLAKE2b-256 checksum How to use checksums |
da25c1c78bd8d0a72b90a4612fabea5d3840b8fcd397f906089dff52fed6dbd4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.17
|
Release files / geneyxpgxparser-0.1.6-cp314-cp314-macosx_10_15_x86_64.whl
| Download URL | geneyxpgxparser-0.1.6-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 |
e26c4ffd714d5675ebf51c97cd818e239a1d5b5f4697c36e37844dc15845b30b
|
|
BLAKE2b-256 checksum How to use checksums |
d95a41080d29677c6f7b303c28cba9c23cf138385c29814e71bdbef7749dae38
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.17
|
Release files / geneyxpgxparser-0.1.6-cp313-cp313-win_amd64.whl
| Download URL | geneyxpgxparser-0.1.6-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
a2bee64cfef8c675600293512cba7f5de902544bed87c6e2527af00a070a586a
|
|
BLAKE2b-256 checksum How to use checksums |
2c2315b96b879851f4eb32ac71ea9856dc74592b91c07b59b22d81fb17142a6f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.17
|
Release files / geneyxpgxparser-0.1.6-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | geneyxpgxparser-0.1.6-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 5.6 MB |
| Tags | CPython 3.13 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
55d549efa8411496458cbab2038b58aff45b7451c9e1da6144f9ad6dc266b385
|
|
BLAKE2b-256 checksum How to use checksums |
c93514c3f99b9cff802578061c6eff98223379130f4828d96b872659f643657e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.17
|
Release files / geneyxpgxparser-0.1.6-cp313-cp313-macosx_10_13_x86_64.whl
| Download URL | geneyxpgxparser-0.1.6-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 |
a1f8c390ad7d345d1f853576db29ff7f1b2a038827cc15b82f1565393a116511
|
|
BLAKE2b-256 checksum How to use checksums |
56c1aec5b1e3cc42e5f0653cebcc594d55d0763191100248946d7afd438f292b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.17
|
Release files / geneyxpgxparser-0.1.6-cp312-cp312-win_amd64.whl
| Download URL | geneyxpgxparser-0.1.6-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
7e3d553314efa4f8b3b8a7717aa5a088d58a13ef5966c0c6740ae8e5870ad1bf
|
|
BLAKE2b-256 checksum How to use checksums |
b05cc787c5e6f2643dda0e1cef094ee67560cc27913b8dc20b9356dcd190f19d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.17
|
Release files / geneyxpgxparser-0.1.6-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | geneyxpgxparser-0.1.6-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 |
32d6a4f9a95289856c0ea66a3faa2d1634bf922d7f3f96b40bb31a779e9a7966
|
|
BLAKE2b-256 checksum How to use checksums |
c1d98bff717fa24ef8e25102c95f42b426ae5a68ec18dbe1e969139f84db685b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.17
|
Release files / geneyxpgxparser-0.1.6-cp312-cp312-macosx_10_13_x86_64.whl
| Download URL | geneyxpgxparser-0.1.6-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 |
191c7f9e5a73faca61088240be11b534c9d85d2aa6b67ac7728e23e72330c67c
|
|
BLAKE2b-256 checksum How to use checksums |
8d16daa3b09468db7f09838400e73f9b2e58a9686cedd13106e6f97039e39965
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.17
|
Release files / geneyxpgxparser-0.1.6-cp311-cp311-win_amd64.whl
| Download URL | geneyxpgxparser-0.1.6-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
a8974edd19833d64f835aa51ca6cff4a6e3979cfefdbcf1bb56d4ba0fd2a2315
|
|
BLAKE2b-256 checksum How to use checksums |
257560d47c8a4c0cf21825cfd16ea093e060c5e422e5e5fdbba43b3541661f47
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.17
|
Release files / geneyxpgxparser-0.1.6-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | geneyxpgxparser-0.1.6-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 5.6 MB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
0e5b7210fb474039667fd77b7494b84decc25d2388acb6f4d2b501f9b9ce5e9c
|
|
BLAKE2b-256 checksum How to use checksums |
b102a6b2383ec37ada8465d0e34418ff3a5da1820cf6e83687d477ec80845cb1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.17
|
Release files / geneyxpgxparser-0.1.6-cp311-cp311-macosx_10_9_x86_64.whl
| Download URL | geneyxpgxparser-0.1.6-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 |
3c0c4f3f357a11c9301f51e7550a0797d04e72ef0e61c6c4dac8be626d143b62
|
|
BLAKE2b-256 checksum How to use checksums |
29ee640ffae71cee13178fcc9c927c1aac38eca8fd9d62f1f918a4f768ba019b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.17
|
Release files / geneyxpgxparser-0.1.6-cp310-cp310-win_amd64.whl
| Download URL | geneyxpgxparser-0.1.6-cp310-cp310-win_amd64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.10 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
f229ae9afe1aa2295cb143acf04aa70fe5794ac264219d3d09206e1766ac1302
|
|
BLAKE2b-256 checksum How to use checksums |
218b4afc5853a0c8b071170898607ae64920c158c13521cab48d0d2d6dcec260
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.17
|
Release files / geneyxpgxparser-0.1.6-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | geneyxpgxparser-0.1.6-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 5.4 MB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
68b38a28deb0a7f74a4f2d9c73baa932944db67e3346249cd23f85322a70db8f
|
|
BLAKE2b-256 checksum How to use checksums |
63a17a03f606f2c49cf2b7cfd776e6b1dc4c4c56723f7dc350f9bb1ad1fd2038
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.17
|
Release files / geneyxpgxparser-0.1.6-cp310-cp310-macosx_10_9_x86_64.whl
| Download URL | geneyxpgxparser-0.1.6-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 |
533f6c677715cc761dee3d337434873494dabfad2280b95ecd486488c076d9f3
|
|
BLAKE2b-256 checksum How to use checksums |
3be38542c9f2c7af8d617969e1f509bf095c15b5870632a8db398b4b1f34478e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.17
|
Release files / geneyxpgxparser-0.1.6-cp39-cp39-win_amd64.whl
| Download URL | geneyxpgxparser-0.1.6-cp39-cp39-win_amd64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.9 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
0be003be3acc6d61c7f64a8cc2403433cac3a328c69caaa7288298d2c35cd676
|
|
BLAKE2b-256 checksum How to use checksums |
6c73392f6ca021f1c7ade896adb44b1dfd4ad393c59747815f7ed066de872a10
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.17
|
Release files / geneyxpgxparser-0.1.6-cp39-cp39-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | geneyxpgxparser-0.1.6-cp39-cp39-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 5.4 MB |
| Tags | CPython 3.9 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
b939929b96f9b313405565a047ef2789012253fe57df0299e362ac01d6b490ec
|
|
BLAKE2b-256 checksum How to use checksums |
a21508d268344591bd0f59f18a33e8adef85d35f800eb5e758412726e8a9728f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.17
|
Release files / geneyxpgxparser-0.1.6-cp39-cp39-macosx_10_9_x86_64.whl
| Download URL | geneyxpgxparser-0.1.6-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 |
18b18ca137c88ce84b3aef0dcd85814061dc67e5ac23fbd27a260fcdd4b5ebed
|
|
BLAKE2b-256 checksum How to use checksums |
7868d6bc4a1b3e95b2d6aeb23190b3b085ad52a5700d5b0b4f0a24ab7c42704e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.17
|
Security for GeneyxPgxParser 0.1.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.