Daniele Nicolodi

> most likely I'll have other questions while I try to figure out whether I can make this transition successfully. Please direct questions to the Beancount mailing list. > So,...

> Sorry, the bug report was a bit strange because in fact it _was_ [a mailing list post](https://groups.google.com/g/beancount/c/9IrHFRmfRzU/m/AbmAm9CGDgAJ) originally, but after a couple weeks with no replies, I thought it...

> It does seem that if the solution is so simple, it might be nice to add a separate directive to beancount to simply process the files that way internally....

> I was imagining a model like the C preprocessor, where each file is parsed, the parse trees for all included files are effectively spliced into place, and then the...

This is indeed the case, but I don't see how this is related to the issue. Can you please elaborate?

This is a known issue caused by how Beancount implements the `import` directive. There is no other workaround that have a `poptag` at the end of `2021.bean` and a `pushtag`...

Tensorflow is not used in Beancount thus the fact that tensorflow_io is pulled in by the Bazel build is probably a shortcoming of the build system. However, building Beancount with...

Beancount 3.0 does not exist yet. There is only a development branch for what may become Beancount 3.0. Getting an usable application out of this branch does not require building...

There is already a PR adding a Meson build definition for the C++ code in v3 #612. With the recent improvements in the tooling for generating Python wheels (distributable Python...

There are two issues: sorting entries on a key that contains `entry.meta["lineno"]` and requiring the `lineno` and `filename` metadata entries. For entries coming from the parser, including `entry.meta["lineno"]` into the...