Daniele Nicolodi

It is also a bit strange that the only comparison operator is `__lt__`. `__eq__` is inherited from `dict` and `__gt__` works for pairs of `Inventory` objects because Python uses `__lt__`...

The idea was to easy the path between v2 and v3 via the possibility to relax the parser to the old behavior in v2. Alternatively, we can make the stricter...

I think implementing the equivalent of the first commit in this series in v3 is an important cleanup of the syntax. I am happy to rebase these changes on v3...

Beancount v2 is in maintenance only: only serious bugs are fixed there. Development happens on the v3 branch. In v3 the import framework has been moved to the `beangulp` project...

`bean-report` has also been removed from the next major release branch of Beancount. The recommended reporting tool is `bean-query` which itself has been moved out of Beancount core into a...

Supporting alternative syntax for expressing the same input data complicates Beancount and associated tools for no real benefit.

I dislike options that change the behavior of the inout syntax non-locally as I believe things are much more clear where minimal information about the context is required to make...

This may help alleviate the burden that this proposed syntax brings on external tools, however, it makes the syntax harder to understand for humans, and I haven't yet understood which...

> How would one attempt to include DR CR notation in beancount? There is no way other than modifying the lexer and the parser. I still don't understand what this...

> because of the negative numbers, a liability viewed in isolation has an upward curve What do you mean by "upward"? Of course negative _y_ axis values on a graph...