On Sun, Apr 20, 2014 at 6:37 PM, Martin Blais <[email protected]> wrote:
> On Sun, Apr 20, 2014 at 9:27 AM, Martin Michlmayr <[email protected]> wrote: > >> Martin, can you share the status of beancount? > > >> 2. I'm forking the import-related code to another project called > Ledgerhub, which will work for Ledger, HLedger and Beancount syntax, and > other similar systems if they materialize. I'll be removing the import code > from Beancount as soon as that's done (I could probably do that now > actually). Ledgerhub already works and that's what I'm using, but same > story there, I'm working to cover it with unit tests before calling an > "official" release. > Quick update: - As of today, the import code that had been living in Beancount's repo has been entirely moved to the LedgerHub project and removed. Beancount does not support import functionality anymore; for that, I would point someone to use Ledgerhub instead. It is now entirely out of the scope of Beancount to support importing, which makes it a more focused project than it was, with less dependencies. - Ledgerhub's port of Beancount's import code does _not_ depend on a Beancount install, it installs entirely independently of it. Four files are still being kept in-sync manually (the basic data definitions), but I suspect that as it evolves I'll eventually break that umbilical cord. Neither project has a release tag on it (again, I want to achieve full test coverage before calling tagging a release); however, I'm already using Ledgerhub's code only for import of all my personal account data and statements, so it works; if you feel brave enough to try it, there is no doc right now, you'll have to read some source. I'll write user documentation for it soon, so it's more palatable (seriously). -- --- You received this message because you are subscribed to the Google Groups "Ledger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
