Martin Blais wrote:
...
> Search the list for various discussion of the current limitations of the
> stable branch.
> See also the discussion here (v3 doc):
> https://docs.google.com/document/d/1qPdNXaz5zuDQ8M9uoZFyyFis7hA0G55BEfhWhrVBsfc/edit#heading=h.vy9jgsdfwj8e
i'm trying to wade through all these various docs and
mentions about precision because i'm trying to figure out
why certain transactions do not balance (and fava complains).
my assumption is that using the Decimal Python type should
remove a lot of internal conversion issues since because the
data is starting out as strings that any calculations should
be as accurate as possible given those strings to start with.
is there a way right now to tell beancount to only use
Decimal internally?
my test data, importer and fava tells me that this doesn't balance:
2000-01-01 * "Split 2 FOR 1"
input: "01/01/2000,20000101-001,Split 2 FOR 1,,INTC,,,,,,,"
transId: "20000101-001"
lot: "43.5 USD, 1999-01-01"
Assets:SB:WHS:INTC -25 INTC {43.5 USD, 1999-01-01} @ 43.5
Assets:SB:WHS:INTC 50 INTC {43.5 USD, 1999-01-01} @ 21.75
i use this at the front of my ledger file:
option "operating_currency" "USD"
option "inferred_tolerance_default" "*:0.001"
option "inferred_tolerance_multiplier" "1.2"
option "infer_tolerance_from_cost" "TRUE"
option "account_rounding" "Equity:RoundingError"
where am i screwing up? :)
fin
--
You received this message because you are subscribed to the Google Groups
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/beancount/qsp6dj-dr5.ln1%40anthive.com.
