retile - simple image conversion and tilemapping
retile can read and write images in either any format understood by imageio, or else in a "raw" format described in a TOML configuration file.
The config file also describes a tile-mapping operation that extracts tiles from the source image, rearranges them as desired, and saves the result - as if repeatedly copying small rectangular regions out of the source image and pasting them onto an output canvas. The dimensions of the output are automatically determined, and the output may be saved in any format.
Detailed explanation pending, as the interface is still being worked out.
retile is offered under a permissive MIT license as described in LICENSE.txt.
1 maintainer
Metadata
1 maintainer
Release files for retile 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| retile-0.2.1-py3-none-any.whl | Python 3 | none | any | Details for retile-0.2.1-py3-none-any.whl |
Release files / retile-0.2.1-py3-none-any.whl
| Download URL | retile-0.2.1-py3-none-any.whl |
|---|---|
| Size | 4.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2ea8501eecb114a5f2025267dc583c72cede0621937d68cf638d661ddfe5ca4d
|
|
BLAKE2b-256 checksum How to use checksums |
333052a5bb3767651d6acd9f3be00ae247691b270c48b330118fcdc8a6aaa50d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.10.12
|
Security for retile 0.2.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
