devlpr is a Python (2.7+ and 3.3+) library to help software developers with their recurrent tasks. It provides a framework for development phases (build, draw dependency graphs, run unit tests, report coverage, etc.) and helpers for some languages (currently Python and OCaml).
It’s licensed under the MIT license. It’s available on the Python package index, its documentation is hosted by Python and its source code is on GitHub.
Questions? Remarks? Bugs? Want to contribute? Open an issue!
Quick start
Install from PyPI:
$ pip install devlpr
Import:
>>> from devlpr import *
Metadata
Release files for devlpr 0.1.0
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 |
|---|---|---|---|---|
| devlpr-0.1.0.tar.gz | 2.5 kB | Without provenance | Details for devlpr-0.1.0.tar.gz |
Release files / devlpr-0.1.0.tar.gz
| Download URL | devlpr-0.1.0.tar.gz |
|---|---|
| Size | 2.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
70e455e54444c8afca1619cdecda6d4d714a2ba9b0cdeb18c50882ed8656a3f2
|
|
BLAKE2b-256 checksum How to use checksums |
cfaaf69976491c9944601822b4f76c8a1be213c802ad382311eade1739586e13
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for devlpr 0.1.0
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.