A lightweight and asynchronous wrapper around the MangaDex v5 API. You can see our stable docs here!
Features
We are currently at 100% feature compliance with the API.
Examples
Please take a look at the examples directory for working examples.
NOTE: More examples will follow as the library is developed.
Current caveats to note
- There are no API endpoints for Artist. It seems they are not differentiated from Author types except in name only.
- I have separated them logically, but under the hood all Artists are Authors and their
__eq__reports as such.
- I have separated them logically, but under the hood all Artists are Authors and their
- The tags and report reasons are locally cached since you must pass UUIDs to the api (and I do not think you're going to memorize those), there's a convenience method for updating the local cache as
Client.update_tagsandClient.update_report_reasonsrespectively.- I have added an example on how to do the above for tags.
- To use these tags, you can see an example here.
- Settings related endpoints are not currently exposed. I have implemented their documented use, but I do not expect them to currently function.
- Once this is exposed fully I will implement a richer interface.
- Currently, if there are any errors in a chapter upload process, the error key does not contain filenames or identifiable information on exactly what file failed upload.
- This means that I locally compare the succeeded files with the ones missing from the full response payload. The examples have been updated with how to check for an error.
- Currently, the
Client.my_chapter_read_historymethod will not work. It is disabled on MD's side due to an issue they had previously. If/when it is re-introduced the method will remain the same.
Further information/tidbits
- For a bit more clarity on a Chapter's
readableAtvspublishAt, see this page on the MangaDex docs. - A query with the
include_future_updatesbool set toTruewill include chapters that are pending release by scanlation groups on MangaDex, but which may be available on their sites.
How to request your own personal OAuth2 Client.
For authentication with hondana to work, you'll need to create and request your own personal OAuth2 client within the MangaDex web portal.
This can be done here (under the "API Clients" section).
Within here you'll want to hit "Create":-
Fill out the relevant name and description of the api client, and hit "Create" once again.
This is currently (as of 10th Nov 2023) still a manual review and approval process by the MangaDex team, so check back regularly to find out if your client is active or still awaiting review.
Once it is active, you can fetch it's client id and client secret:-
You then pass this information to the hondana.Client constructor alongside your username and password for MangaDex, as this will be used to authenticate you within the API.
Contributing
If you would like to contribute to Hondana, please take a look at the contributing guidelines and follow the procedure there.
If you have any question please feel free to join my Discord server:
1 maintainer
Metadata
1 maintainer
Release files for hondana 3.7.6
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 | |
|---|---|---|---|---|
| hondana-3.7.6.tar.gz | 373.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hondana-3.7.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 517.2 kB
Release files / hondana-3.7.6.tar.gz
| Download URL | hondana-3.7.6.tar.gz |
|---|---|
| Size | 373.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fe75ac07d7b62ba3d22d83c72b5f19c6518174eae57a35cd7198f8ba588511e8
|
|
BLAKE2b-256 checksum How to use checksums |
df5a34f540e63f4d9d4aa2efceeea75cea4a7ac865a360ee6adde7c3aacc4e8e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.3 {"installer":{"name":"uv","version":"0.13.3","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / hondana-3.7.6-py3-none-any.whl
| Download URL | hondana-3.7.6-py3-none-any.whl |
|---|---|
| Size | 143.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8e92c0ceb8833fde328ca9effdd38f30e2ec9aa32707d70882b3a17282323958
|
|
BLAKE2b-256 checksum How to use checksums |
0985423745e77eb8d0486ea950ef303732036d039cdb27b467eef30cec086afe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.3 {"installer":{"name":"uv","version":"0.13.3","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for hondana 3.7.6
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.
