On 18/08/24 21:26, Chary Chary wrote:
Martin,
It is weird to use a public mailing list to address a single person.
Are you expecting only Martin to answer?
correct me if I am wrong, but I think the beancount's *pad *directive
conflicts with the *Round-Tripping guarantee*, the way it is described
here:
https://docs.google.com/document/d/1QftxNvQPdH-MikMBHupftU6F4IsNZP5FlFh1LCbVgk8/edit#heading=h.qs8b7mcsjj82
In particular, Beancount offers the guarantee that the output of the
printer should always be parseable and should result in the same data
structure when read back in. (It should be considered a bug if that is
not the case.)
I think it may be worth mentioning this in the documentation
I don't understand what you mean.
The property described there holds true:
>>> from beancount.parser import parser, printer
>>> entries, errors, options = parser.parse_string(
... 2024-08-17 open Assets:Foo
...
... 2024-08-18 pad Assets:Foo Equity:Opening-Balances
... ''')
>>> printer.print_entries(entries)
2024-08-17 open Assets:Foo
2024-08-18 pad Assets:Foo Equity:Opening-Balances
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/0c5c7060-cde1-4386-b1ec-1a1fa21047dc%40grinta.net.
