no_symcache_no_problem: be more tolerant of not-yet-implemented provider backends #39
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "no_symcache_no_problem"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
A workaround for cases where broker/data backends don’t yet implement a sym-cache (intro-ed in GH commit
0050232) and break on fqme lookup while processing a trades ledger..Instead, this patch attempts to allow bypassing this, BUT it’s pretty flaky (at best) and will definitely fail on multiple mkts loaded into a single chart..
See history of
.data._symcachehere to grok how-n-why it was added; more or less it avoids re-downloading the mkt-pair set from a provider every time the backend boots, reducing startup time.Specific hack-around for the moment..
only_require: list[str]|TrueinAccount.update_from_ledger()to allow the caller to avoid raising failedmkt: MktPair = symcache.mktmaps[fqme]lookups on symbols it doesn’t care about; this will obvi happen when thesymcacheisn’t populated due to lacking backend support.Other improvements/tweaks landing here
.accounting.Symbol, it was replaced long ago on GH byMktPair.9e6bfa0926toc3f3b25524c3f3b25524to81693cc2f781693cc2f7to577da2e8e3no_symcache_no_problem: be more tolerant of not-yet-implemented provider backendsto no_symcache_no_problem: be more tolerant of not-yet-implemented provider backends577da2e8e3to07fbe859c3