pykabu-calendar
Japanese earnings calendar aggregator.
Installation
pip install pykabu-calendar
Quick Start
import pykabu_calendar as cal
# Get earnings calendar (uses all sources by default)
df = cal.get_calendar("2026-02-10")
# Use specific sources only
df = cal.get_calendar("2026-02-10", sources=["matsui", "tradersweb"])
# Without historical inference (faster)
df = cal.get_calendar("2026-02-10", infer_from_history=False)
# Export to CSV
cal.export_to_csv(df, "earnings.csv")
# Export to Parquet (requires pyarrow)
cal.export_to_parquet(df, "earnings.parquet")
# Export to SQLite
cal.export_to_sqlite(df, "earnings.db")
# Load back from SQLite
df = cal.load_from_sqlite("earnings.db", date="2026-02-10")
# Health check all data sources
cal.check_sources()
Output Columns
| Column | Description |
|---|---|
code |
Stock code (e.g., "7203") |
name |
Company name |
datetime |
Best estimate datetime |
confidence |
Confidence level: "highest", "high", "medium", or "low" |
during_trading_hours |
Whether datetime falls within TSE trading hours |
candidate_datetimes |
List of candidate datetimes (most likely first) |
ir_datetime |
Datetime from company IR page |
sbi_datetime |
Datetime from SBI |
matsui_datetime |
Datetime from Matsui |
tradersweb_datetime |
Datetime from Tradersweb |
inferred_datetime |
Datetime inferred from history |
past_datetimes |
List of past earnings datetimes |
Features
- Aggregates earnings calendars from SBI, Matsui, Tradersweb
- Discovers company IR pages and extracts exact announcement times
- Infers announcement time from historical patterns (via pykabutan)
- Parallel source fetching for faster results
- Source health checks via
check_sources() - YAML-based source configuration for easy maintenance
- Exports to CSV, Parquet, and SQLite
- EarningsSource ABC for adding custom sources
Data Source Priority
- IR page - Company's official IR page (most accurate)
- Inferred - From historical patterns
- SBI - SBI Securities (JSONP API)
- Matsui - Matsui Securities
- Tradersweb - Tradersweb
Documentation
Full documentation: https://obichan117.github.io/pykabu-calendar
License
MIT
Metadata
Release files for pykabu-calendar 0.9.2
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 | |
|---|---|---|---|---|
| pykabu_calendar-0.9.2.tar.gz | 67.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pykabu_calendar-0.9.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 109.6 kB
Release files / pykabu_calendar-0.9.2.tar.gz
| Download URL | pykabu_calendar-0.9.2.tar.gz |
|---|---|
| Size | 67.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
37ddb5d730ad94ce4cac02deca1d1416356b92968933da3b601c9790ba61dee4
|
|
BLAKE2b-256 checksum How to use checksums |
ba7010e5afafc60fa06338dc08faf900452e872f8eed3789ac99e3c3e8ab3338
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.0
|
Release files / pykabu_calendar-0.9.2-py3-none-any.whl
| Download URL | pykabu_calendar-0.9.2-py3-none-any.whl |
|---|---|
| Size | 41.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b6fc8634b8e74c31e43549d555f9a8e791358f4b7dddc2ab64e5cfcb1999d349
|
|
BLAKE2b-256 checksum How to use checksums |
5d3a6be11617518674ba846a817e99f8450ac3c6a5388a8edc8575df812c39fb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.0
|
Security for pykabu-calendar 0.9.2
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.