On 19/08/24 09:51, Chary Chary wrote:
On Sunday, August 18, 2024 at 9:42:16 PM UTC+2 [email protected] wrote:
I don't understand what you mean.
What I mean, is that *pad *statement causes beancount to insert a
padding transaction
I think there is a fundamental misunderstanding.
The statement you quote from the documentation says that the
serialization of the ledger to file (implemented in the
beancount.parser.printer Python module) is read back by the beancount
parser (implemented in the beancount.parser.parser Python module)
resulting in the same data structure.
This statement is true also in the case of "pad" directives, as proven
with the code in my other message. There is nothing special done with
"pad" directives in the parser.
It is not the parser that adds the transactions that implement the
padding accordingly to the "pad" and "balance" entries in the ledger.
This job is done by the booking code. There are many other
transformations done by the booking code (the main one being completing
postings in the transactions adding the inferred amounts and prices).
Cheers,
Dan
--
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/a8a53c0c-9909-4a18-a20b-17fc12b8111b%40grinta.net.
