Installation
bletl is available through PyPI:
pip install bletl
For Developers
You can use bletl by installing it in your Python environment.
- clone it
git clone https://github.com/JuBiotech/bletl cd bletlpip install -e .to install it into your (activated!) Python environment in "editable mode"
Contributing
The easiest way to contribute is to report bugs by opening Issues.
If you want to contribute, you should...
- Clone
bletl - Create a new branch
- Make changes on your feature-branch
- Open a Pull Request
Usage and Citing
bletl is licensed under the GNU Affero General Public License v3.0.
When using bletl in your work, please cite the Osthege & Tenhaef et al. (2022) paper and the corresponding software version.
Note that the paper is a shared first co-authorship, which can be indicated by 1 in the bibliography.
@article{bletlPaper,
author = {Osthege$^1$, Michael and
Tenhaef$^1$, Niklas and
Zyla, Rebecca and
Müller, Carolin and
Hemmerich, Johannes and
Wiechert, Wolfgang and
Noack, Stephan and
Oldiges, Marco},
title = {bletl - A Python package for integrating {B}io{L}ector microcultivation devices in the {D}esign-{B}uild-{T}est-{L}earn cycle},
journal = {Engineering in Life Sciences},
volume = {22},
number = {3-4},
pages = {242-259},
keywords = {BioLector, feature extraction, growth rate, microbial phenotyping, uncertainty quantification},
doi = {https://doi.org/10.1002/elsc.202100108},
url = {https://onlinelibrary.wiley.com/doi/abs/10.1002/elsc.202100108},
eprint = {https://onlinelibrary.wiley.com/doi/pdf/10.1002/elsc.202100108},
year = {2022}
}
@software{bletl,
author = {Michael Osthege and
Niklas Tenhaef and
Laura Helleckes and
Carolin Müller},
title = {JuBiotech/bletl: v1.1.0},
month = feb,
year = 2022,
publisher = {Zenodo},
version = {v1.1.0},
doi = {10.5281/zenodo.6284777},
url = {https://doi.org/10.5281/zenodo.6284777}
}
Head over to Zenodo to generate a BibTeX citation for the latest release.
Metadata
Release files for bletl 1.8.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 |
|---|---|---|---|---|
| bletl-1.8.0.tar.gz | 56.0 kB | Without provenance | Details for bletl-1.8.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bletl-1.8.0-py3-none-any.whl | Python 3 | none | any | Details for bletl-1.8.0-py3-none-any.whl |
Total release size: 105.6 kB
Release files / bletl-1.8.0.tar.gz
| Download URL | bletl-1.8.0.tar.gz |
|---|---|
| Size | 56.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
013beb5a4795d1b366fa7589ca69ce4b8c75f939595c93da8b002add12117fad
|
|
BLAKE2b-256 checksum How to use checksums |
4d7fc8d429715a76a54f1632f0f0a127e82b2664409e0c177841c9502240a97b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Release files / bletl-1.8.0-py3-none-any.whl
| Download URL | bletl-1.8.0-py3-none-any.whl |
|---|---|
| Size | 49.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3acc1e5899ede468a57be25e58ed3845b8aaa477ed2697f36549feb5786a09d1
|
|
BLAKE2b-256 checksum How to use checksums |
7769f26db456e0ce34028a9d74653f8b10cd76d6f6e09100b601d807364cdf41
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Security for bletl 1.8.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.