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
755 B
Plaintext
39 lines
755 B
Plaintext
Date,Dividends
|
|
2019-12-13,0.086000
|
|
2020-06-25,0.015000
|
|
2022-03-25,0.196000
|
|
2022-09-23,0.096000
|
|
2024-12-13,0.399000
|
|
2022-06-24,0.141000
|
|
2023-09-22,0.072000
|
|
2024-03-21,0.115000
|
|
2018-03-22,0.113000
|
|
2023-12-22,0.121000
|
|
2026-06-25,0.127000
|
|
2019-03-21,0.062000
|
|
2021-06-24,0.078000
|
|
2021-12-23,0.073000
|
|
2024-06-27,0.089000
|
|
2025-06-26,0.196000
|
|
2018-09-14,0.066000
|
|
2023-06-27,0.106000
|
|
2023-03-24,0.152000
|
|
2025-12-12,0.169000
|
|
2016-12-21,0.054000
|
|
2017-09-21,0.065000
|
|
2020-03-26,0.034000
|
|
2021-09-23,0.082000
|
|
2022-12-23,0.167000
|
|
2017-03-23,0.092000
|
|
2019-06-14,0.016000
|
|
2019-09-25,0.165000
|
|
2024-09-26,0.128000
|
|
2025-03-27,0.117000
|
|
2025-09-25,0.106000
|
|
2026-03-26,0.034000
|
|
2017-06-22,0.081000
|
|
2017-12-21,0.069000
|
|
2018-06-21,0.086000
|
|
2018-12-18,0.112000
|
|
2020-12-24,0.042000
|