first import the package on your terminal with pip:
pip3 install im2txt
next you import the module:
import im2txt
now you just need to encode the image of your preference:
im2txt.encode('/path/to/image/pooptest.jpg')
you will receive a pooptest.txt file.
This file will have the pixel value of all pixels on the image.
To decode the .txt file back to an image we use:
im2txt.decode('path/to/txtfile/pooptest.txt')
you will receive the encoded image back again in form of .png!
Metadata
Release files for im2txt 0.0.3
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 | |
|---|---|---|---|---|
| im2txt-0.0.3.tar.gz | 1.9 kB | Without provenance | Details |
Release files / im2txt-0.0.3.tar.gz
| Download URL | im2txt-0.0.3.tar.gz |
|---|---|
| Size | 1.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8bd79b1700502019473139a27222b4eae1ed75f21e4f7c34f8ec6b4a66ca54bb
|
|
BLAKE2b-256 checksum How to use checksums |
4a41b586a5c1e19a17786fdb70837229dcd61516de2929cdcf101b46b7daeed7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.15.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.36.1 CPython/3.6.0
|
Security for im2txt 0.0.3
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.