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-03-15,0.141000
|
|
2020-03-20,0.170000
|
|
2024-06-21,0.180000
|
|
2026-06-18,0.252000
|
|
2017-06-16,0.131000
|
|
2017-09-15,0.147000
|
|
2019-06-21,0.152000
|
|
2025-09-19,0.215000
|
|
2024-09-20,0.202000
|
|
2025-12-19,0.219000
|
|
2019-09-20,0.151000
|
|
2019-12-20,0.139000
|
|
2021-09-17,0.192000
|
|
2022-03-18,0.183000
|
|
2023-06-16,0.180000
|
|
2022-12-16,0.131000
|
|
2026-03-20,0.262000
|
|
2025-03-21,0.200000
|
|
2018-12-21,0.133000
|
|
2020-06-19,0.153000
|
|
2020-12-18,0.155000
|
|
2023-12-15,0.177000
|
|
2024-12-20,0.242000
|
|
2016-12-16,0.112000
|
|
2017-12-15,0.124000
|
|
2021-03-19,0.166000
|
|
2025-06-20,0.211000
|
|
2018-03-16,0.129000
|
|
2018-06-15,0.146000
|
|
2021-06-18,0.151000
|
|
2023-03-17,0.198000
|
|
2024-03-15,0.159000
|
|
2017-03-17,0.084000
|
|
2018-09-21,0.111000
|
|
2020-09-18,0.152000
|
|
2022-09-16,0.181000
|
|
2023-09-15,0.180000
|