iocp tries to mimic Go’s io.Copy function (http://golang.org/pkg/io/#Copy) which copies from everything that is an io.Reader to anything that is an io.Writer).
The Python world of things is not that organized, so iocp.copy will try to do a best guess about which are the right function to call when reading and writing.
For example, checking md5 signature of a file:
md5 = hashlib.md5()
with open('/path/to/file') as fo:
iocp(fo, md5)
print md5.hexdigest()
1 maintainer
Metadata
1 maintainer
Release files for iocp 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 |
|---|---|---|---|---|
| iocp-0.1.0.tar.gz | 1.7 kB | Without provenance | Details for iocp-0.1.0.tar.gz |
Release files / iocp-0.1.0.tar.gz
| Download URL | iocp-0.1.0.tar.gz |
|---|---|
| Size | 1.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
31f78163a168c84d852307dd8459176bcec274450ab480bec566fa1410e7928d
|
|
BLAKE2b-256 checksum How to use checksums |
c96abc4620ad2d6d14cc6445c8661d0c64dc0c7b9b2f9fe5dff341fbcf9a53a8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for iocp 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.
