On 10/06/24 11:33, Stefano Zacchiroli wrote:
On Mon, Jun 10, 2024 at 11:04:11AM +0200, Daniele Nicolodi wrote:
- Release at least beangulp, beanquery, and benaprice on PyPI. I released
beangulp recently. I'm planning to clean up some loose ends in beanquery and
release a 0.1.0 version soon. beanprice probably needs some cleanups too. I
can take care of that too, if there are no other volunteers. Is there any
other component moved to other repositories that people use?
How about Fava?
I hope the Fava maintainers will make Fave compatible with beancount
3.0.0 once we release it. I don't use Fava and I'm not familiar with its
implementation.
As I understand it, Fava is currently incompatible with beanquery as a
separate project, or at least I'm regularly getting syntax errors(!)
when executing within Fava queries that work fine with beanquery (split
out) and beancount 2.x.
I don't know how Fava integrates BQL queries. I suspect that it imports
beancount.query and uses the API. Therefore, instlling beanquery
alongside beancount 2.x does not make Fava use it as beanquery does not
install anything in the beancount namespace.
Maybe your lower profile plan for a beancount 3.0 release (which I like
a lot) can help with that too.
I think a beanquery release would be sufficient for this. Fava could
then either depend on beanquery (and use the nicer beanquery API) or
could try to import beanquery and fall back to beancount.query, allowing
users that install beanquery to use the new features.
I'll try to have a beanquery release out this week.
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 on the web visit
https://groups.google.com/d/msgid/beancount/bfb981cb-f9d1-4ce9-a8e2-6c898d3505c1%40grinta.net.
