Yahoo's 2026 event-feed change (capitalGain events dropped for some funds; no events at all for terminated tickers) can wipe good event history on re-download. Defense in depth: - overrides/event-backup/: last-known-good copy of every dividend/ capitalGain file (8,192 files, 58 MB); refresh with scripts/backup_events.py after each dump update - data.py event_file(): frozen > data-root (while populated) > backup; used by panel reads, verify_official, and the double-listing scanner - README: capital-gain files are mutual-fund-only in this dump; Yahoo has no LT/ST split (tax.py taxes capg at lt_rate; the per-fund split would come from fund-company annual tax statements or commercial feeds) - tests: exact Timestamp .loc keys (pandas 3.x string matching returns a Series on large DatetimeIndex)
40 lines
775 B
Plaintext
40 lines
775 B
Plaintext
Date,Dividends
|
|
2017-09-26,0.291000
|
|
2019-06-25,0.131000
|
|
2021-12-23,0.278000
|
|
2023-03-23,0.211000
|
|
2023-06-22,0.191000
|
|
2023-09-21,0.300000
|
|
2018-06-26,0.078000
|
|
2021-03-22,0.126000
|
|
2025-09-04,0.309000
|
|
2017-03-28,0.052000
|
|
2019-12-24,0.203000
|
|
2021-06-21,0.106000
|
|
2024-09-26,0.248000
|
|
2024-12-27,0.238000
|
|
2026-03-05,0.200000
|
|
2016-12-28,0.033000
|
|
2022-03-24,0.147000
|
|
2022-06-23,0.213000
|
|
2025-06-05,0.164000
|
|
2017-12-27,0.128000
|
|
2020-03-23,0.283000
|
|
2021-09-23,0.187000
|
|
2022-12-22,0.321000
|
|
2024-06-27,0.300000
|
|
2025-03-06,0.229000
|
|
2017-06-27,0.093000
|
|
2018-09-25,0.121000
|
|
2019-03-26,0.119000
|
|
2020-09-21,0.213000
|
|
2023-12-27,0.298000
|
|
2026-06-04,0.112000
|
|
2020-06-22,0.109000
|
|
2025-12-30,0.617000
|
|
2018-03-27,0.085000
|
|
2018-12-24,0.145000
|
|
2020-12-21,0.247000
|
|
2022-09-22,0.224000
|
|
2024-03-21,0.244000
|