phlorest
A cldfbench plugin to curate language phylogenies.
Install
pip install phlorest
Usage
Bootstrapping a phlorest-curated dataset
phlorest provides a cldfbench dataset template to create the skeleton of files and directories for a
phlorest-curated dataset, to be run with cldfbench new.
Running
cldfbench new --template phlorest
will create a dataset skeleton looking as follows
$ tree testtree/
testtree/
├── cldf
│ └── README.md
├── cldfbench_testtree.py
├── etc
│ ├── characters.csv
│ └── taxa.csv
├── metadata.json
├── raw
│ └── README.md
├── setup.cfg
├── setup.py
└── test.py
Implementing CLDF creation
Implementing CLDF creation means - as for any other cldfbench-curated dataset - filling in the
cmd_makecldf method of the Dataset subclass in cldfbench_<id>.py.
The CLDF writer which can be accessed as args.writer within cmd_makecldf is an instance of
phlorest.CLDFWriter, which has convenience methods to add summary- or posterior trees to the CLDF
dataset. At least a summary is needed to make a dataset valid. Adding one looks as follows
args.writer.add_summary(
self.raw_dir.read_tree(...),
self.metadata,
args.log)
Running CLDF creation
With cmd_makecldf implemented, CLDF creation can be triggered running
cldfbench makecldf cldfbench_<id>.py
The resulting CLDF dataset can be validated running
pytest
Release workflow
cldfbench makecldf --glottolog-version v5.2 --with-cldfreadme cldfbench_<id>.py
pytest
cldfbench zenodo --communities phlorest cldfbench_<id>.py
cldfbench readme cldfbench_<id>.py
phlorest check --with-R cldfbench_<id>.py
git commit -a -m"release vX.Y"
git push origin
phlorest release cldfbench_<id>.py vX.Y
Dependencies
The run_treeannotator method of Dataset requires the treeannotator command from BEAST to be
installed. For details on how to install treeannotator (and BEAST), see https://beast.community/index.html
Metadata
Release files for phlorest 2.0.0
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 | Actions |
|---|---|---|---|---|
| phlorest-2.0.0.tar.gz | 30.4 kB | Without provenance | Details for phlorest-2.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| phlorest-2.0.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for phlorest-2.0.0-py2.py3-none-any.whl |
Total release size: 62.2 kB
Release files / phlorest-2.0.0.tar.gz
| Download URL | phlorest-2.0.0.tar.gz |
|---|---|
| Size | 30.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2552f2118f52e02e803b2bc2a97423a8e21f3c207e93c6110c84e1f1bff2b27f
|
|
BLAKE2b-256 checksum How to use checksums |
3a9dd93df15351125e5f46b543024a8f70bf4dc9e4efb56529045f1768a64321
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.3
|
Release files / phlorest-2.0.0-py2.py3-none-any.whl
| Download URL | phlorest-2.0.0-py2.py3-none-any.whl |
|---|---|
| Size | 31.9 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
195ecb8b42bcaa642219b8e8cccbc3852417dcac0853e6dcb5158b3654dd0017
|
|
BLAKE2b-256 checksum How to use checksums |
33c08b07f73810604f1fb7778201e4785a961981334cbc486e9cac572d58a7ef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.3
|
Security for phlorest 2.0.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.