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
|
|
2022-12-14,0.405000
|
|
2024-06-27,0.085000
|
|
2019-06-27,0.052000
|
|
2019-09-27,0.052000
|
|
2021-06-29,0.067000
|
|
2022-03-30,0.062000
|
|
2024-03-27,0.074000
|
|
2017-12-15,0.038000
|
|
2018-06-28,0.041000
|
|
2021-09-29,0.066000
|
|
2021-12-15,0.442000
|
|
2020-09-29,0.059000
|
|
2023-06-29,0.083000
|
|
2023-09-28,0.082000
|
|
2025-12-15,0.059000
|
|
2020-06-29,0.058000
|
|
2021-03-30,0.057000
|
|
2022-06-29,0.083000
|
|
2023-12-13,0.067000
|
|
2024-09-27,0.075000
|
|
2025-09-29,0.076000
|
|
2023-03-30,0.075000
|
|
2025-03-28,0.070000
|
|
2025-06-27,0.082000
|
|
2017-06-29,0.016000
|
|
2018-09-27,0.049000
|
|
2019-12-17,0.056000
|
|
2020-03-30,0.050000
|
|
2024-12-13,0.060000
|
|
2026-06-29,0.077000
|
|
2017-09-28,0.036000
|
|
2018-03-28,0.034000
|
|
2018-12-18,0.061000
|
|
2022-09-29,0.076000
|
|
2019-03-28,0.035000
|
|
2020-12-16,0.059000
|
|
2026-03-30,0.071000
|