sharrow
numba for ActivitySim-style spec files
Building a Wheel
To build a wheel for sharrow, you need to have build installed. You can
install it with python -m pip install build.
Then run the builder:
python -m build .
Building the documentation
Building the documentation for sharrow requires JupyterBook.
jupyterbook build docs
Developer Note
This repository's continuous integration testing will use ruff to check code
quality. There is a pre-commit hook that will run ruff on all staged files
to ensure that they pass the quality checks. To install and use this hook,
run the following commands:
python -m pip install pre-commit # if needed
pre-commit install
Then, when you try to make a commit, your code will be checked locally to ensure that your code passes the quality checks. If you want to run the checks manually, you can do so with the following command:
pre-commit run --all-files
If you don't use pre-commit, a service will run the checks for you when you
open a pull request, and make fixes to your code when possible.
Metadata
Release files for sharrow 2.16.2
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 |
|---|---|---|---|---|
| sharrow-2.16.2.tar.gz | 2.4 MB | Without provenance | Details for sharrow-2.16.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sharrow-2.16.2-py3-none-any.whl | Python 3 | none | any | Details for sharrow-2.16.2-py3-none-any.whl |
Total release size: 4.6 MB
Security for sharrow 2.16.2
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.