This release is a pre-release and may not be stable for production use.
Documentation · Installation · Guide · API reference · Migrate · Citations
geckopy
Enzyme-constrained genome-scale metabolic modelling in Python: the Python port of the GECKO Toolbox (MATLAB). It builds on cobrapy and raven-toolbox, and reads and writes the same ecModel YAML files as GECKO, so ecModels move between the two toolboxes without conversion.
An ecModel adds the limits of enzymes to a genome-scale model: each enzyme has a finite capacity (its kcat) and the cell has a finite protein budget. geckopy fetches kcats from BRENDA, predicts them with DLKcat, tunes them against growth and flux data with CMA-ES, applies custom curations and integrates proteomics.
Status: beta (
4.0.0b2). The yeast-GEM tutorial runs end to end. The major and minor version follow GECKO, which is why it starts at 4.
Not the older geckopy. This is a new port of GECKO. It is unrelated to the earlier
geckopyon PyPI (release 2.0.2 and earlier), described in Carrasco Muriel, Long & Sonnenschein, Microbiology Spectrum 11(6):e01705-23 (2023), doi:10.1128/spectrum.01705-23.
Install
Both geckopy and raven-toolbox are pre-releases, so pip needs --pre:
pip install --pre geckopy
Extras: geckopy[tutorial] (matplotlib), geckopy[evotune] (cma, for kcat tuning) and geckopy[dev] (pytest and ruff). Python 3.11 or newer.
Quick start
A minimal build, for a project folder with model_adapter.toml, models/ and data/:
from geckopy import ModelAdapter, load_conventional_gem, load_uniprot_tsv, make_ec_model, save_ec_model
adapter = ModelAdapter.from_folder("my_project")
model = load_conventional_gem(adapter)
uniprot = load_uniprot_tsv(adapter.params.path / "data" / "uniprot.tsv")
ec_model = make_ec_model(model, adapter, uniprot_db=uniprot)
save_ec_model(ec_model, "ecModel.yml", adapter=adapter)
The guide covers each step: Getting started, Building an ecModel and Gathering kcats. Every public function is available as from geckopy import X; geckopy.__all__ lists them, and the API reference documents them. The full protocol, with kcat curation, proteomics and Crabtree-effect simulation, is tutorials/full_ecModel/protocol.py. Fitting kcats to measured growth and fluxes is described in docs/evotune_kcat_tuning.md.
Documentation and parity with GECKO
The protocol, installation, troubleshooting and API reference for both toolboxes are at gecko-docs. The ecModel YAML format is described in the guide and in docs/yaml_format.md. geckopy ports GECKO function by function, and each source file names its MATLAB original. The parity ledger records, for every public function, whether the two agree and why where they do not.
Cite us
If you have used geckopy in your work, please cite the GECKO protocol:
Chen Y, Gustafsson J, Tafur Rangel A, Anton M, Domenzain I, Kittikunapong C, Li F, Yuan L, Nielsen J & Kerkhoven EJ. Reconstruction, simulation and analysis of enzyme-constrained metabolic models using GECKO Toolbox 3.0. Nature Protocols 19, 629-667 (2024). doi:10.1038/s41596-023-00931-7.
License
MIT. See LICENSE.
Metadata
Release files for geckopy 4.0.0b2
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 |
|---|---|---|---|---|
| geckopy-4.0.0b2.tar.gz | 5.6 MB | With provenance | Details for geckopy-4.0.0b2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| geckopy-4.0.0b2-py3-none-any.whl | Python 3 | none | any | Details for geckopy-4.0.0b2-py3-none-any.whl |
Total release size: 5.9 MB
Release files / geckopy-4.0.0b2.tar.gz
| Download URL | geckopy-4.0.0b2.tar.gz |
|---|---|
| Size | 5.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7b5551961e7b0e78c046083cdedc8bf8c8b08e1ca2b9bfe056cd1dbe7e29b9b4
|
|
BLAKE2b-256 checksum How to use checksums |
cbe2c2eef8f851bf92ecf5fad6773af6d307c7eb50289c9847bf28c460c12b23
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 2, 2026.
Transparency logRelease files / geckopy-4.0.0b2-py3-none-any.whl
| Download URL | geckopy-4.0.0b2-py3-none-any.whl |
|---|---|
| Size | 339.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c87e14f3b51b4d55be719c80c306a49f2620794c0068b8feb42d6e6989932c0f
|
|
BLAKE2b-256 checksum How to use checksums |
1fcab80ff1834b7f09ff573458272f3eb1c1a7ef450e8943e814395b301032ef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 2, 2026.
Transparency logSecurity for geckopy 4.0.0b2
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 geckopy-4.0.0b2.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 Nov 2, 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.