Are there any plans to migrate beangrow and fava to v3?

[Eric Morgan]

Since v2 is not very much maintained longer, I'd like to move to v3. I'm currently using fava and beangrow in a project. Are there any plans to move those over to v3 anytime soon?

[Red S]

This is the only related issue I could find at Fava’s github page. Perhaps making a request over at github might get their attention?

I might be mistaken, but Beangrow looks like it could use perhaps use a maintainer and active contributors. Curious, have you tried running it to see if it works with v3 right now?

​

[Red S]

Also: others seem to report using Fava with v3 (using pipx for example), which makes me think it works out of the box, and simply needs its dependencies updated to include v3. I haven't personally tried it though.

[Martin Blais]

On Thu, Sep 12, 2024 at 6:41 PM Red S <redst...@gmail.com> wrote:

This is the only related issue I could find at Fava’s github page. Perhaps making a request over at github might get their attention?

I might be mistaken, but Beangrow looks like it could use perhaps use a maintainer and active contributors.

+1 to that.

I haven't used it myself since 2021.

 

Curious, have you tried running it to see if it works with v3 right now?

On Wednesday, September 11, 2024 at 5:05:15 PM UTC-7 Eric Morgan wrote:

Since v2 is not very much maintained longer, I'd like to move to v3. I'm currently using fava and beangrow in a project. Are there any plans to move those over to v3 anytime soon?

--
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+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/0853e8e8-c452-44ce-86e9-03e08e1e7de9n%40googlegroups.com.

[Stefano Zacchiroli]

On Thu, Sep 12, 2024 at 03:41:13PM -0700, Red S wrote:
> This is the only related issue

> <https://github.com/beancount/fava/issues/1831> I could find at Fava’s

> github page. Perhaps making a request over at github might get their
> attention?

There is also https://github.com/beancount/fava/issues/1824 (referenced
from the previous one), but the underlying issue is likely the same.

Cheers
--
Stefano Zacchiroli . za...@upsilon.cc . https://upsilon.cc/zack _. ^ ._
Full professor of Computer Science o o o \/|V|\/
Télécom Paris, Polytechnic Institute of Paris o o o </> <\>
Co-founder & CTO Software Heritage o o o o /\|^|/\
https://twitter.com/zacchiro . https://mastodon.xyz/@zacchiro '" V "'

[Brian Lalor]

Adding Jakob, who’s been actively working on Fava.  Jakob, anything we can do to get v3 support pulled in?

— 

Brian Lalor (he/him)

bla...@bravo5.org

--
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+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/20240913064514.3norhoeiggxunjuf%40upsilon.cc.

[c79m...@gmail.com]

I tried using using beanquery with Fava, and wasn't able to get anywhere about 4 months ago.  I'm not much of a programmer, but Fava appears to be pretty tightly coupled to V2's beanquery interface, and would need some decent reworking to use the seperated out beanquery of V3.   Unfortunately, I don't have the skills, or time to do that. :-(     (I was interested in using a couple of new beanquery features to generate a report, but wound up just kludging the data together in python to get the same end result. )

Cameron Murphy

[Mariano Draghi]

yagebu seems to be working as of last week on a version of Fava that would be compatible with both Beancount v2 and v3, using the standalone beanquery package.

* meta-issue tracking the work: https://github.com/beancount/fava/issues/1860

* the (currently WIP) PR: https://github.com/beancount/fava/pull/1859

-- 

Mariano 

[ma...@jakobschnitzer.de]

Yep, I'm working on the PR that Mariano linked to support both Beancount v2 and v3 in parallel - I'll probably merge that to main in the coming days, then this can see some wider testing :)

[Red S]

Great! Thank you for all the work you put in to develop, maintain, and bring us Fava, yagebu!

[Daniele Nicolodi]

On 17/10/24 23:10, ma...@jakobschnitzer.de wrote:
> Yep, I'm working on the PR that Mariano linked to support both Beancount
> v2 and v3 in parallel - I'll probably merge that to main in the coming
> days, then this can see some wider testing :)

Hello Jakob,

I had a very cursory look at the PR a while ago and I noticed that you
are using some parts of beanquery that I would consider private API and
implementation details that are very likely to change.

I didn't comment on the PR at that time because I was planning to
publish some documentation for beanquery soon, including some API
documentation, and that would have helped define how to do what you need
with what is intended to be the public API. Unfortunately, I haven't
really had as much time as I was hoping to work on the documentation,
thus it hasn't materialized yet. Therefore, this is a warning that some
of the parts of beanquery you are accessing are likely to change.

I would suggest to wait a little bit before merging your PR and work on
getting what you need into the public beanquery API. Knowing that you
are working on this, I'll prioritize getting minimal API documentation
out ASAP, most likely over the weekend.

Cheers,
Dan