Ah thanks for the updates Martin and Daniele! I run a lot of reporting scripts each month (returns, income, budgeting, etc), and really those and the tests I run to make sure those work as expected are what take the most time for me, so that's nothing to do with beancount itself.
Excited about parsing updates though! That'll make importing expenses so much nicer since the in-editor checks just re-run bean-check on each change, and my ledger has gotten a bit long. On Monday, January 6, 2025 at 3:06:01 PM UTC-6 Daniele Nicolodi wrote: > On 05/01/25 21:12, Aaron Stacy wrote: > > I upgraded to beancount v3 and I'm happy I did with the type annotations > > and more focused deps (i.e. breaking out beangulp & others from the > core). > > > > Only thing that surprised me though was that it seems slightly slower > > (maybe a percentage point or so). I've got about 15k entries in my > > ledger, and I've got a few plugins. My implicit prices directive wraps > > beancount.prices.implicit_prices. This is on an M1 macbook. > > > > As I said, v3 is for sure an over all improvement, but let me know if > > yall know of anything I'm missing out on here or if this is expected. > > I don't remember when the change landed exactly and whether it is > included in the 3.0 release, but we switched to the regex package to > evaluate some regular expression to correctly validate account names > containing non-ASCII characters. As the regular expressions are more > complex, this may have introduced a slight slowdown. > > There is work underway to speed up the parser, but nothing had been > merged yet and I have been busy with other things. > > 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 visit https://groups.google.com/d/msgid/beancount/28a25872-4d56-43a1-a07b-53cbb85bb273n%40googlegroups.com.
