Moose Frank
A Python package packed with tools that are commonly used in Moose projects.
Development
See the CONTRIBUTING guide.
Installation
pip install moose-frank
Local testing
isort
docker-compose run --rm --no-deps python isort [module/path] [options]
flake8
docker-compose run --rm --no-deps python flake8 [module/path]
black
docker-compose run --rm --no-deps python black [module/path]
pytest
docker-compose run --rm --no-deps python coverage run ./runtests.py
Translations
Updating translations
docker-compose run --rm --no-deps manage makemessages -l nl --no-wrap --no-location --no-obsolete
docker-compose run --rm --no-deps manage compilemessages
Metadata
Release files for moose-frank 10.0.3
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 |
|---|---|---|---|---|
| moose_frank-10.0.3.tar.gz | 19.8 kB | Without provenance | Details for moose_frank-10.0.3.tar.gz |
Release files / moose_frank-10.0.3.tar.gz
| Download URL | moose_frank-10.0.3.tar.gz |
|---|---|
| Size | 19.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
77adecb9b69d1c26079b4cda168a1325f2b958a6f919f73d26cbcb276aa873c5
|
|
BLAKE2b-256 checksum How to use checksums |
3fa14d2d720e7a4fe9672d3b3c44bea84a9317b6dbcbd443b1c9f722d4ad7599
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/8.0.0 pkginfo/1.11.1 requests/2.25.1 requests-toolbelt/1.0.0 tqdm/4.66.4 CPython/3.11.9
|
Security for moose-frank 10.0.3
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.