deltadash.py
A simple, dependency-less library for programatically interfacing with DeltaDash's file formats.
Current features
deltadash.py currently includes the following features:
- Difficulty reading and deserialisation
- Difficulty writing and deserialisation
Example
Here is an example of how to read, modify and write a DeltaDash map through the deltadash.py library!
# deltadash.py map reading example
from deltadash.maps.difficulty import Difficulty
# Read a .dd file
diff = Difficulty.from_file("test_res/debug.dd")
# Print the difficulty's full name
print(diff.full_name)
# Change the difficulty name
diff.name = "New Name"
# Write the difficulty to a new file
diff.into_file("test_res/debug_new.dd")
You may view more examples in the examples directory of this repo!
1 maintainer
Metadata
1 maintainer
Release files for deltadash 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 |
|---|---|---|---|---|
| deltadash-0.1.0.tar.gz | 6.3 kB | Without provenance | Details for deltadash-0.1.0.tar.gz |
Release files / deltadash-0.1.0.tar.gz
| Download URL | deltadash-0.1.0.tar.gz |
|---|---|
| Size | 6.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2cef8b5922b9363b6d326df1a43e2c9fb04b07cdf49d5317831734d52b84fcb9
|
|
BLAKE2b-256 checksum How to use checksums |
33955c1f6a6b2ba2d49f7def7bc02e6ba8059173b19797c1f528b91dc771967c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.6
|
Security for deltadash 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.
