The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for httpopen 0.1.1
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 | |
|---|---|---|---|---|
| httpopen-0.1.1.tar.gz | 2.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| httpopen-0.1.1-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 5.5 kB
Release files / httpopen-0.1.1.tar.gz
| Download URL | httpopen-0.1.1.tar.gz |
|---|---|
| Size | 2.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3c6476befb44bf6387898653216d5856115889e0dfbaddad2d676bee0850c700
|
|
BLAKE2b-256 checksum How to use checksums |
6edd235d0497c4fd7ff5b445f015f2f2630f366611cfd14b1ee47df66e2bc8a4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.9.13
|
Release files / httpopen-0.1.1-py2.py3-none-any.whl
| Download URL | httpopen-0.1.1-py2.py3-none-any.whl |
|---|---|
| Size | 2.9 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
be3b212b356706c2a9df01a03e362b7c7d0bd8a8eae998b8bda0d1b3b3e3814a
|
|
BLAKE2b-256 checksum How to use checksums |
50392b0485e471d1eb803c7d436020b93b2a360964e0c66420fd2b8bf91a58c7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.9.13
|
Security for httpopen 0.1.1
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.
