On 18/06/24 10:13, Stefano Zacchiroli wrote:
On Tue, Jun 18, 2024 at 03:36:34PM +0800, Martin Michlmayr wrote:
* Stefano Zacchiroli <[email protected]> [2024-06-18 09:27]:
I welcome migration tips on what's the easiest migration path (to
beangulp, I guess?)
Yes.
Thanks, although I'm still a bit confused.
This document
https://docs.google.com/document/d/1hBfsHZcoHgz5rvhCdP42g2FJ5ouycIMV4H1tfgXpwBU/
"Importing External Data in Beancount" is about v3 ("This document is
about Beancount v3, under development, and a work in progress.") and
Beangulp, but still talks about bean-extract as an executable involved
in importing transactions with v3/beangulp.
What am I missing?
The "under development, and a work in progress" warning refers to the
content of the document rather than to the subject of the document :-)
The best documentation there is for beangulp is the example included in
the repository
https://github.com/beancount/beangulp/tree/master/examples and the
docstrings in the code.
In a nutshell, to upgrade from beancount.ingest to beangulp, it shoul be
sufficient to modify all Python imports from the beancount.ingest
namespace to the beangulp namespace and to turn the configuration file
that was used to be passed to bean-extract into a self-standing script
as demonstrated here
https://github.com/beancount/beangulp/blob/master/examples/import.py
Then, calling such script with a '--help' argument should be enough to
understand how to use it.
A second (optional) step would be to update the importers from the old
beangulp.ImporterProtocol interface to the new beangulp.Importer
interface, which allows to implement some new features.
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/1a88d6ff-4ef5-4bd6-9a28-360244e6eeb5%40grinta.net.
