This release is a pre-release and may not be stable for production use.
Introduction
TODO
Usage
TODO
Installation
ezpy can be installed via pip install ezpy as usual, see releases for an overview of available versions. To get a bleeding-edge version from source, use these commands:
repo="jhermann/ezpy"
pip install -r "https://raw.githubusercontent.com/$repo/master/requirements.txt"
pip install -UI -e "git+https://github.com/$repo.git#egg=${repo#*/}"
As a developer, to create a working directory for this project, call these commands:
git clone "https://github.com/jhermann/ezpy.git" cd "ezpy" command . .env --yes --develop # add '--virtualenv /usr/bin/virtualenv' for Python2 invoke build check
You might also need to follow some setup procedures to make the necessary basic commands available on Linux, Mac OS X, and Windows.
References
1 maintainer
Metadata
1 maintainer
Release files for ezpy 0.1.0.dev0
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 |
|---|---|---|---|---|
| ezpy-0.1.0.dev0.zip | 17.2 kB | Without provenance | Details for ezpy-0.1.0.dev0.zip |
Release files / ezpy-0.1.0.dev0.zip
| Download URL | ezpy-0.1.0.dev0.zip |
|---|---|
| Size | 17.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2fd1400c21d4dee29aca9411834d5a66437710db3c0bacdd7c6772cf30af9353
|
|
BLAKE2b-256 checksum How to use checksums |
2c05c4ed74b3a45eeab7d784e54531ca251f1c45344ebe00d348fd6dcc9709b0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for ezpy 0.1.0.dev0
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.
