Re: beangulp and writing out one file per account

[Martin Blais]

This would get useful indeed. Maybe we should support an importer returning a Dict[str, List[Transaction]] or adding metadata with the intended "file group", and a separate stage that writes out files (or better: inserts the transaction group before unique tags from a set of Beancount files). 

Now that there are three independent ideas in the previous paragraph:

- file groups so that an importer can return more than one list of files

- routing these (or just the output of each importer) to multiple locations

- automatic insertion of imported transactions in a specific place in a file

On Wed, Oct 19, 2022, 03:33 Red S <redst...@gmail.com> wrote:

I use one file per real-world account, which looks like:

beancount/

  main.bc # includes the other files

  accounts/

     Assets.Banks.ABCDBank.Checking.bc

     Assets.Investments.Taxable.BTrade.bc

     Liabilities.Credit-Cards.Blue-Mastercard-0123.bc

I use this patch to extract.py in beancount to have my importers output to multiple files.

From this mailing list, I gather several users use organizations that involve multiple files, split in different ways. So I'm wondering whether custom importer output is something beangulp can support. Happy to think about a patch for this if so. Or if there's a better way to do this, I'd be open to that as well.

--
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 beancount+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/a0ca348e-0cff-462c-8eef-96580f365bbcn%40googlegroups.com.