Simyan
A Python wrapper for the Comicvine API.
Installation
pip install Simyan
Example Usage
from datetime import timedelta
from pathlib import Path
from simyan.comicvine import Comicvine
session = Comicvine(
api_key="Comicvine API Key",
cache_path=Path("cache.sqlite"), # Optional, defaults to ~/.cache/simyan/cache.sqlite
cache_expiry=timedelta(days=1), # Optional, defaults to 14 days
ratelimit_path=Path(
"ratelimits.sqlite"
), # Optional, defaults to ~/.cache/simyan/ratelimits.sqlite
)
# Search for Publisher
results = session.list_publishers(params={"filter": "name:DC Comics"})
for publisher in results:
print(f"{publisher.id} | {publisher.name} - {publisher.site_url}")
# Get details for a Volume
result = session.get_volume(volume_id=26266)
print(result.summary)
Documentation
Bugs/Requests
Please use the GitHub issue tracker to submit bugs or request features.
Contributing
- When running a new test for the first time, set the environment variable
COMICVINE__API_KEYto your Comicvine API key. The responses will be cached in thetests/cache.sqlitedatabase without your key.
Socials
1 maintainer
Metadata
1 maintainer
Release files for Simyan 4.2.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 | |
|---|---|---|---|---|
| simyan-4.2.0.tar.gz | 12.2 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| simyan-4.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.3 MB
Release files / simyan-4.2.0.tar.gz
| Download URL | simyan-4.2.0.tar.gz |
|---|---|
| Size | 12.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
18210626a4d5d969c603b77ccad55cc86754e127076529b0a14541fce9a4f15b
|
|
BLAKE2b-256 checksum How to use checksums |
7cade1ccfa9e698e4eb7a4e2d37142c1442f9c2ac2fbf5655bebfa6ecb8e451b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 30, 2026.
Transparency logRelease files / simyan-4.2.0-py3-none-any.whl
| Download URL | simyan-4.2.0-py3-none-any.whl |
|---|---|
| Size | 33.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
33c371c780d7f504601ef9be973c98b446616a047a55e9d24b6cc7ce6f1578c7
|
|
BLAKE2b-256 checksum How to use checksums |
617c2c64a957d47b75c371703ca22c4838ee743cf1ec348445efa6b060190cba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 30, 2026.
Transparency logSecurity for Simyan 4.2.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 simyan-4.2.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 Sep 30, 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.
