On Sat, Feb 3, 2024 at 7:24 AM Daniele Nicolodi wrote:
> On 31/01/24 22:23, Chary Chary wrote:
> > Dan,
> >
> > I thought that the main idea of beancount v3 was migrating some
> > functionality to C++ to make the thing be faster.
> >
> > If this is not being done in beancount v3, are there any other
> > improvements which make it worth using as an opposite to v2 at the
> moment?
>
> The C++ rewrite has seen significant progress but it has never landed in
> a form where it can be used from a beancount application.
>
That's correct. It stalled on two things:
- not much free time to play with open source anymore (sad)
- a decent kludge I had to make passing protobufs between Python and C++
got taken away in a change in protobuf itself
I've pretty much decided to explore Rust as an alternative (not much
progress, again, no time to play)
> The major change in the v3 branch is that beancount.ingest has been
> split of and significantly restructured into the beangulp project, that
> beancount.query has been split of into the beanquery project and
> significantly improved, that the deprecated bean-report and bean-web
> functionality have been removed, and several other cleanups. A detailed
> list of changes has not been compiled.
>
> 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 beancount+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beancount/8e4ad0b7-e480-4cfd-866a-8f995dd424dd%40grinta.net
> .
>
--
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 beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/beancount/CAK21%2BhN2sLNvGVojq8HkGt%3Dz-GhQgPGbBVqF7Lq9Avw%2B8OjpjQ%40mail.gmail.com.
