libvcell
libvcell is a subset of VCell algorithms intended to support the pyvcell python package.
- Github repository: https://github.com/virtualcell/libvcell/
- Documentation https://virtualcell.github.io/libvcell/
Getting started with your project
First, create a repository on GitHub with the same name as this project, and then run the following commands:
git init -b main
git add .
git commit -m "init commit"
git remote add origin git@github.com:virtualcell/libvcell.git
git push -u origin main
Finally, install the environment and the pre-commit hooks with
make install
You are now ready to start development on your project! The CI/CD pipeline will be triggered when you open a pull request, merge to main, or when you create a new release.
To finalize the set-up for publishing to PyPI or Artifactory, see here. For activating the automatic documentation with MkDocs, see here. To enable the code coverage reports, see here.
Releasing a new version
- Create an API Token on PyPI.
- Add the API Token to your projects secrets with the name
PYPI_TOKENby visiting this page. - Create a new release on Github.
- Create a new tag in the form
*.*.*. - For more details, see here.
Repository initiated with fpgmaas/cookiecutter-poetry.
1 maintainer
Metadata
1 maintainer
Release files for libvcell 0.0.22
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| libvcell-0.0.22-py3-none-win_amd64.whl | Python 3 | none | Windows x86-64 | Details |
| libvcell-0.0.22-py3-none-win32.whl | Python 3 | none | Windows x86-32 | Details |
| libvcell-0.0.22-py3-none-macosx_13_0_arm64.whl | Python 3 | none | macOS 13.0+ ARM64 | Details |
Total release size: 115.7 MB
Release files / libvcell-0.0.22-py3-none-win_amd64.whl
| Download URL | libvcell-0.0.22-py3-none-win_amd64.whl |
|---|---|
| Size | 40.4 MB |
| Tags | Python 3 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
e13fda4f3eb6a4df6e89cdc87b4bd8deeb69de471612aa2f79dbecc442bf8bf2
|
|
BLAKE2b-256 checksum How to use checksums |
96d2b1d8258f3e114957b6c11635dab2dfd3a2315634c18144fbbe68c04a57d1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.5.1 CPython/3.10.11 Windows/10
|
Release files / libvcell-0.0.22-py3-none-win32.whl
| Download URL | libvcell-0.0.22-py3-none-win32.whl |
|---|---|
| Size | 40.4 MB |
| Tags | Python 3 Windows x86-32 |
|
SHA-256 checksum How to use checksums |
8d91e71af7089fa8b7dd8b030bc2f379728b777c181862c8b3f65bd1dbc492a6
|
|
BLAKE2b-256 checksum How to use checksums |
1241945891e4a86ab18194d9421173b21d9938d975cc3b49a88d44db2fa3b11e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.5.1 CPython/3.10.11 Windows/10
|
Release files / libvcell-0.0.22-py3-none-macosx_13_0_arm64.whl
| Download URL | libvcell-0.0.22-py3-none-macosx_13_0_arm64.whl |
|---|---|
| Size | 34.9 MB |
| Tags | Python 3 macOS 13.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
51265628af5c8f00fcdec02e91aba1fa9366cc1bb2819e77af756b7e068865bb
|
|
BLAKE2b-256 checksum How to use checksums |
d401d419a3e97685c6a0601b3b46562180d6da30e994400f8047c3e9c8373c6e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.5.1 CPython/3.14.7 Darwin/24.6.0
|
Security for libvcell 0.0.22
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.
