State of average cost booking in v3

[Red S]

I see this thread where average cost booking was rolled back in v2 due to a performance regression. The thinking then seemed to be that it would be easier to defer implementing this to v3.

I was wondering if avg cost booking is already in v3, or if not, if at all there is a rough sense of when it might possibly be on v3, or if it's unknown right now?

Thank you!

[Martin Blais]

On Sun, Oct 9, 2022 at 5:45 PM Red S <redst...@gmail.com> wrote:

I see this thread where average cost booking was rolled back in v2 due to a performance regression. The thinking then seemed to be that it would be easier to defer implementing this to v3.

I was wondering if avg cost booking is already in v3, or if not, if at all there is a rough sense of when it might possibly be on v3, or if it's unknown right now?

Unknown. I have too much work that's higher priority than Beancount over the last couple of years and too many other higher priority items to make meaningful progress on new features for v3 so far. Much of the codes I wanted to fork out of it have been moved to other projects, so that's progress of a kind. On the status of new things: there's a new parser, the next step is I want to figure out how to properly link and expose the protobufs to Python (there are 2-3 ways that aren't great, and one good way to do it, I prototyped but haven't hooked it up yet), and to then replace the parser component with the newer, better C++ parser that's largely done, carefully comparing the old parser's output with the new.

[Red S]

Good to know, thank you, Martin!