On Friday, March 13, 2026 at 12:46:02 PM UTC+1 [email protected] wrote:
but it seems like a LOT of people (not least of which if fava) end up reinventing the wheel of building up inventories in python code and reducing them with the price map in various different ways to try to be more efficient than calling BQL repeatedly. I was one of those people. I have this class <https://github.com/Ev2geny/evbeantools/blob/97f637d9a599d077239f8a9556776a3c82817b4c/src/evbeantools/summator.py#L248-L259> : class BeanSummator(): """ Simulates a beanquery SUM command for aggregating transaction amounts by account up to a specified date as used in the below beanquetry query: SELECT root(n, account) as shortened_acc, sum(position) WHERE date <= {date} AND account ~ "accounts_re" GROUP BY shortened_acc This class enhances efficiency by remembering the last sum calculated and the date for which it was calculated. It ensures that subsequent sums are requested for the same or later dates, allowing reuse of previous calculations. This approach speeds up the calculation process, especially beneficial when determining net worth across multiple dates Marimo looks really promising, Indeed! so I'm off to convert my collection of scripts & Google Sheet/beancount hybrids & jupyter notebooks to Marimo...... Just out of curiosity, How did you use Google Sheets in all of this? -- 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 visit https://groups.google.com/d/msgid/beancount/e57bb60c-d49e-4df4-8c2e-c6311ead5896n%40googlegroups.com.
