FABM and python
This folder contains source and build tools to compile and build FABM as a python module. In addition a number of useful scripts are included.
When configuring for compilation using CMake and additional target ‘wheel’ is added - either in VisualStudio or in Makefile - depending on platform. The taget ‘wheel’ will build a ‘.whl’ file that can be installed using pip.
This is mainly for developers/release managers as a few additional steps are still required.
It is the intention to have up-to-date wheels for some platforms on release.
1 maintainer
Metadata
1 maintainer
Release files for pyfabm 0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyfabm-0.1-py2.py3-none-win_amd64.whl | Python 3, Python 2 | none | Windows x86-64 | Details for pyfabm-0.1-py2.py3-none-win_amd64.whl |
Release files / pyfabm-0.1-py2.py3-none-win_amd64.whl
| Download URL | pyfabm-0.1-py2.py3-none-win_amd64.whl |
|---|---|
| Size | 1.1 MB |
| Tags | Python 2 Python 3 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
dd95335b48c3e91689d4433f465d3817374ea5b583084987decd9473c81151d3
|
|
BLAKE2b-256 checksum How to use checksums |
63de8b1805991583d822634ac1956e385898621bbe4aa86bb6da56c0b06f0d88
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.19.1 setuptools/39.0.1.post20181012 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.6.5
|
Security for pyfabm 0.1
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.
