I am very close to completing reimplementation of quote downloading in
ledger 3 (it works completely on my machine but doesn't report problems in
any sane way). I have addressed bugs 174 (configurable getquote path) and
411 (don't keep trying to download if you receive a stale price). Right
now I am adding some sanity checking to the options and working on error
reporting. I should be able to push this to git within the next few days.
I need some advice on how people would prefer to handle the following
situations:
NOTE: ledger assumes the getquote script returns the latest available price.
1. Stale results: If getquote returns a price that is stale (age exceeds
the --price-exp) should ledger silently accept that as the latest price,
accept it and generate a warning, or generate an error and quit? Right now
I have it silently accepting the stale value.
2. Valid Option combinations: --download does nothing if -V isn't
specified. Should ledger silently accept this, warn about the missing -V
option or stop and report?
I had hoped to address bug 588 ('getquote' only queries one commodity at a
time, which can be slow) but this requires some significant changes to the
internal flow ledger takes (ledger deals with commodities immediately as
they are parsed, grouping commodities for a batch download would require
two passes through the journal files)
--
Craig, Corona De Tucson, AZ
enderw88.wordpress.com
