fimama - Fictional Map Maker
This is a hobby project which aims to create a map maker program (not a web app) for fictional (not just fantasy) worlds.
I'll start with a Voronoi cell based heightmap and see how much I can be bothered to work on this.
If things do progress I do have the following aims:
- The Changelog includes some more specific potential features
- I have more ideas than are listed there, but time is limited.
Some general principles:
- The project will Keep a Changelog.
- The project will use semantic version numbering.
- The project will aim for pythonic code and good documentation.
- Keep backwards compatibility so that old maps should mostly be openable by later versions.
- Make most features editable, and make most features lockable when regenerating random features.
- Tests will be written as well but instead of code coverage, the priority is on integration tests.
What I wont most likely do:
- I do not intend to write any plate tectonics, but will be happy to integrate them if somebody else writes the code.
If you want to contribute, please get in touch.
1 maintainer
Metadata
1 maintainer
Release files for fimama 0.9.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 | |
|---|---|---|---|---|
| fimama-0.9.0.tar.gz | 229.5 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fimama-0.9.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 277.0 kB
Release files / fimama-0.9.0.tar.gz
| Download URL | fimama-0.9.0.tar.gz |
|---|---|
| Size | 229.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2973fcbf5b41ad875d781c5ea0bf1e9ea4558b4c711528d2467398149718399c
|
|
BLAKE2b-256 checksum How to use checksums |
0ccd055a7c761f24996b8f0ffdbd66fd652efac6be5c5ed212239bf23cff4c09
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 21, 2026.
Transparency logRelease files / fimama-0.9.0-py3-none-any.whl
| Download URL | fimama-0.9.0-py3-none-any.whl |
|---|---|
| Size | 47.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3fa19a2af56e9e5a0392a5d1204c1cdb1f40219b9d677746e59284a11a7decb5
|
|
BLAKE2b-256 checksum How to use checksums |
851480dfdc5e20ae783c8a89c1841c7dc4bab1affe33130c203cd2d47d9425ae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 21, 2026.
Transparency logSecurity for fimama 0.9.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for fimama-0.9.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 21, 2026.
Transparency logA 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.
