phylogenetic
Compatibility alias package for bijux-phylogenetics.
This distribution installs the canonical phylogenetics runtime under the
shorter phylogenetic package and CLI names. It is not a reduced runtime and
it is not a fork. It points at the same benchmark, workflow, and reporting
surfaces that the canonical package publishes.
Alias Structure At A Glance
- shorter install name
- shorter CLI name
- same canonical runtime behavior
Install
phylogenetic supports Python 3.11 and newer.
python3.11 -m pip install phylogenetic
phylogenetic --help
What You Still Get
Installing the alias package still gives you access to the same documented runtime depth:
| Capability family | What carries through the alias |
|---|---|
| Trees and alignments | inspection, validation, comparison, and preparation workflows |
| Native runtime | native likelihood and native inference surfaces |
| Comparative analysis | comparative and ancestral workflows |
| Reporting | benchmark, workflow, and reporting surfaces |
| External engines | governed wrapper-backed external-engine workflows |
What The Alias Does Not Change
- it does not remove native inference surfaces
- it does not remove comparative, ancestral, or parsimony families
- it does not change the evidence-book or quality reading model
- it does not publish a smaller scientific contract than the canonical package
Choose this package when you want the shorter install and command names while keeping the same public runtime contract.
Choose the canonical bijux-phylogenetics package instead when you want the
most explicit package name for notebooks, papers, release notes, or downstream
documentation.
Shorter Python Workflow Surface
The alias keeps the same workflow API surface under the shorter
phylogenetic.api import path.
from pathlib import Path
from phylogenetic.api import (
render_report_workflow,
run_comparative_model_workflow,
run_sequence_to_tree_workflow,
)
workflow = run_sequence_to_tree_workflow(
Path("dataset/sequences.fasta"),
out_dir=Path("artifacts/sequence-to-tree"),
sequence_type="dna",
)
comparative = run_comparative_model_workflow(
Path("dataset/tree.nwk"),
Path("dataset/traits.tsv"),
response="response",
predictors=["predictor_one"],
lambda_value=1.0,
)
report = render_report_workflow(
tree_path=workflow.output_paths["tree"],
alignment_path=workflow.output_paths["trimmed_alignment"],
traits_path=Path("dataset/traits.tsv"),
metadata_path=Path("dataset/metadata.tsv"),
out_path=Path("artifacts/sequence-to-tree/report.html"),
)
workflow.write_json(Path("artifacts/sequence-to-tree/workflow.json"))
workflow.write_tsv(Path("artifacts/sequence-to-tree/workflow.tsv"))
comparative.write_tsv(Path("artifacts/comparative-model.tsv"))
Use the alias when you want the shorter import and command surface:
from phylogenetic.api import ...phylogenetic --help
Use the canonical runtime name when you want the most explicit package name in public artifacts, papers, release notes, or downstream documentation:
from bijux_phylogenetics.api import ...bijux-phylogenetics --help
Read This Next
Metadata
Release files for phylogenetic 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| phylogenetic-0.1.2.tar.gz | 10.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| phylogenetic-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 17.5 kB
Release files / phylogenetic-0.1.2.tar.gz
| Download URL | phylogenetic-0.1.2.tar.gz |
|---|---|
| Size | 10.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
20bfec23d4056f4f9ad3db822edfb018eae00ac9589dc7e47dd6815a4a9de896
|
|
BLAKE2b-256 checksum How to use checksums |
16fcb52c1f6bf245980fdc89a614a33282d2808839a5e84e7e36b24ba5c63f17
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 5, 2026.
Transparency logRelease files / phylogenetic-0.1.2-py3-none-any.whl
| Download URL | phylogenetic-0.1.2-py3-none-any.whl |
|---|---|
| Size | 6.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c7748c65ba94dc606e87755026db1da0bf0ba28dbb60896fd69b8cf0ca3dae7c
|
|
BLAKE2b-256 checksum How to use checksums |
276a83f622b8012c171fa39a787d404a6bd9de75f10ad963d82159d078600988
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 5, 2026.
Transparency logSecurity for phylogenetic 0.1.2
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for phylogenetic-0.1.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 5, 2026.
Transparency logA 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.