simbio
A Python-based package for simulation of Chemical Reaction Networks (CRNs).
It extends poincare,
a package for modelling dynamical systems,
to add functionality for CRNs.
Usage
See simbio's documentation on the dyscolab page, or go directly to the intro tutorial.
Install
Using pixi, install from PyPI with:
pixi add --pypi simbio
or install the latest development version from GitHub with:
pixi add --pypi simbio@https://github.com/dyscolab/simbio.git
Otherwise,
use pip or your pip-compatible package manager:
pip install simbio # from PyPI
pip install git+https://github.com/dyscolab/simbio.git # from GitHub
Development
This project is managed by pixi. You can install it for development using:
git clone https://github.com/dyscolab/simbio
cd simbio
pixi run pre-commit-install
Pre-commit hooks are used to lint and format the project.
Testing
Run tests using:
pixi run test
Publishing to PyPI
When a tagged commit is pushed to GitHub,
the GitHub Action defined in .github/workflows/ci.yml
builds and publishes the package to PyPI.
Tag a commit and push the tags with:
git tag <my-tag>
git push --tags
Trusted publishing must be enabled once in PyPI Publishing. Fill the following values in the form:
PyPI Project Name: simbio
Owner: maurosilber
Repository name: simbio
Workflow name: ci.yml
Environment name: pypi
Metadata
Release files for simbio 1.2.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 |
|---|---|---|---|---|
| simbio-1.2.0.tar.gz | 25.0 kB | Without provenance | Details for simbio-1.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| simbio-1.2.0-py3-none-any.whl | Python 3 | none | any | Details for simbio-1.2.0-py3-none-any.whl |
Total release size: 57.1 kB
Release files / simbio-1.2.0.tar.gz
| Download URL | simbio-1.2.0.tar.gz |
|---|---|
| Size | 25.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2e9d7d37c21c7d6857f050a39c65b7681bef7e9d4551053477d009bcc1d12cf2
|
|
BLAKE2b-256 checksum How to use checksums |
c0a8171e0aa209e2af2bbbf50a35736210051238cabdc5d2e8e89967d32570c4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.9 {"installer":{"name":"uv","version":"0.12.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / simbio-1.2.0-py3-none-any.whl
| Download URL | simbio-1.2.0-py3-none-any.whl |
|---|---|
| Size | 32.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f8ca32766d699a577ca64ce8eedf61ca732152a74708aaf2f842909d59f2346b
|
|
BLAKE2b-256 checksum How to use checksums |
0c5d18007681c5c6a7424b3940a49e85ca221013acc8e0f971561434fa7ee2a0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.9 {"installer":{"name":"uv","version":"0.12.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for simbio 1.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.