Because srsly wtf :) :) :| :| :(
Usage
from parse_requirements_not_suckily import parse_requirements
Later that day… (in setup.py)
install_requires=parse_requirements()
You be all like “wat no filler garbage code, like batteries included lol?” and I be all like “yes”
License
Copyright (c) 2016 Jon Robison
See included LICENSE for licensing information
Metadata
Release files for parse-requirements-not-suckily 1.0.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 | |
|---|---|---|---|---|
| parse-requirements-not-suckily-1.0.0.tar.gz | 1.8 kB | Without provenance | Details |
Release files / parse-requirements-not-suckily-1.0.0.tar.gz
| Download URL | parse-requirements-not-suckily-1.0.0.tar.gz |
|---|---|
| Size | 1.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3d878cac6a848caa9391eba823f90db4c14631665661c350d82983970cb67e38
|
|
BLAKE2b-256 checksum How to use checksums |
cb3a3ef754352295b8ba50cc72c56af2e52c0860936d74ee5b3d6c45306deb38
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for parse-requirements-not-suckily 1.0.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.