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)
39 lines
764 B
Plaintext
39 lines
764 B
Plaintext
Date,Dividends
|
|
2018-06-22,2.500000
|
|
2021-06-23,3.459000
|
|
2025-12-15,20.397000
|
|
2019-12-16,19.375000
|
|
2020-09-23,0.769000
|
|
2020-12-15,30.182000
|
|
2020-03-24,0.832000
|
|
2021-03-24,0.700000
|
|
2024-06-21,2.849000
|
|
2024-12-16,27.751000
|
|
2026-03-24,0.329000
|
|
2017-06-23,5.679000
|
|
2017-12-15,25.973000
|
|
2018-09-21,1.013000
|
|
2021-12-15,27.368000
|
|
2022-12-15,18.848000
|
|
2023-09-22,0.654000
|
|
2025-03-24,0.379000
|
|
2018-03-22,0.813000
|
|
2022-09-23,0.621000
|
|
2023-06-23,1.263000
|
|
2024-03-21,0.513000
|
|
2025-06-23,0.412000
|
|
2024-09-23,0.535000
|
|
2019-03-22,0.824000
|
|
2019-06-21,6.481000
|
|
2020-06-23,7.278000
|
|
2022-03-24,0.622000
|
|
2022-06-23,2.062000
|
|
2023-03-24,0.579000
|
|
2023-12-15,37.782000
|
|
2017-09-22,0.972000
|
|
2018-12-17,35.010000
|
|
2021-09-23,0.678000
|
|
2025-09-23,0.431000
|
|
2019-09-23,0.877000
|
|
2026-06-23,6.561000
|