Thank you for the comprehensive response, Martin (and Ben too, for sharing)! It's helpful to know what's been done and the rough things in the pipeline next, not to mention, super exciting!
*For other curious users:* - I installed v3 just to check it out, though I'll probably stick with v2 simply because I don't have enough time in the day currently to deal with even minor breakage, but YMMV. My experience is below: - Martin's post confirms v3 is being developed by replacing code paths in v2 as opposed to being built from scratch. This is what enables you to switch to v3 any time you want (and are willing to risk occasional breakage) - I installed using "pip install ." in master - fava works fine with v3, though it needs a trivial patch to account for beancount.ingest moving over to beangulp (sed 's/from beancount.ingest/from beangulp/' fava/core/ingest.py) - as Martin mentioned, booking and core are the same as v2, so you'll see no performance difference Have core C++ rewrites made it much faster than v2? > > Oh yes. Parsing is roughly 10x faster. Night and day. (But there's no > booking yet and no core library yet, so there's no point.) > Very cool! -- 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/e88134a6-ce3a-45c0-a3ae-c1b23178dc0en%40googlegroups.com.
