sopel-mangadex
A MangaDex plugin for Sopel IRC bots
Installing
Releases are hosted on PyPI, so after installing Sopel, all you need is pip:
$ pip install sopel-mangadex
Using
sopel-mangadex automatically shows information about mangadex.org links in
recognized formats:
- Series:
https://mangadex.org/title/<UUID>[/<optional_slug>]
e.g.https://mangadex.org/title/de900fd3-c94c-4148-bbcb-ca56eaeb57a4/spice-and-wolf - Chapter:
https://mangadex.org/chapter/<UUID>[/<optional_page_number>
e.g.https://mangadex.org/chapter/3fed674e-663f-44d2-bc99-6145600fd46a/7
Output examples
Series page
<Sopel> [MangaDex] Ookami to Koushinryou | Content: 🟢
| 💯 Completed | Monsters, Animals, Romance, Adventure,
Fantasy, Slice of Life, Supernatural, Adaptation | Synopsis:
With his carthorse as his only companion, the young merchant
Kraft Lawrence slowly wends his way through dusty back roads
in search of profitable trade. But this monotony screeches to
a halt when, one night, he encounters a harvest goddess in
the guise of a beautiful […]
Chapter link
<Sopel> [MangaDex] (unknown title) | Chapter 1, page 7 of Kono Bijutsubu
ni wa Mondai ga Aru!
This particular chapter doesn't have a title of its own.
Series title language precedence
This plugin prioritizes romaji (ja-ro) titles, then English (en), then
finally falls back on Japanese (ja). If none of those translations exist, you
will see "Unknown title".
Note that some series may have incorrect language tags that make this logic
appear to break. For example, at time of writing, Kono Bijutsubu ni wa Mondai
ga Aru! from the sample chapter link output above has its romaji title tagged
as en instead of ja-ro. These cases need to be fixed on the MangaDex side;
trying to detect them in sopel-mangadex would be too fiddly.
Chapters only have one (optional) title string, in the language of that translation.
Changelog
0.1.0
First release of sopel-mangadex.
Handles the basics: Links to series pages, links to chapters.
Metadata
Release files for sopel-mangadex 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 | |
|---|---|---|---|
| sopel_mangadex-0.1.0.tar.gz | 4.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sopel_mangadex-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.0 kB
Release files / sopel_mangadex-0.1.0.tar.gz
| Download URL | sopel_mangadex-0.1.0.tar.gz |
|---|---|
| Size | 4.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
74cc6d5142516447f987f4ef24f51712e3ece515f56de573552502e231c5f617
|
|
BLAKE2b-256 checksum How to use checksums |
aba7a4f111257f42b6683674d5f02eb0868a851a8f29eff6cbc6ff8cfeb1cfc6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 31, 2026.
Transparency logRelease files / sopel_mangadex-0.1.0-py3-none-any.whl
| Download URL | sopel_mangadex-0.1.0-py3-none-any.whl |
|---|---|
| Size | 5.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ad4f4d63b86f34b247fb901b0916bb150f98746c2ef2e67d7f34794bba58ed18
|
|
BLAKE2b-256 checksum How to use checksums |
10c609d998404a8362717218bf94c9bb36cea12ce6f65457fd6ba0dbe70afa45
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 31, 2026.
Transparency log