Thank you!
I had those changes already, but I don't have a fix for this one yet.
from beancount.utils.text_utils import replace_numbers
ModuleNotFoundError: No module named 'beancount.utils.text_utils'
On Thu, Apr 7, 2022 at 1:14 PM Ben Blount wrote:
> Here you go. My process was just to
Here you go. My process was just to attempt running Fava and fix
imports until it works.
diff --git a/src/fava/core/ingest.py b/src/fava/core/ingest.py
index d94a8bce..7d483bbf 100644
--- a/src/fava/core/ingest.py
+++ b/src/fava/core/ingest.py
@@ -14,9 +14,9 @@ from typing import Tuple
from
Hi,
You mention here you required some changes to import names in fava. Can you
please share your changes?
Does v3 support multiple includes without having to repeat options in each
file?
Thanks!
On Tuesday, February 8, 2022 at 1:06:45 PM UTC-6 b...@bben.us wrote:
> Fava, importers, and
On 08/02/2022 12:33, Colin Ingarfield wrote:
Hello,
About a year ago I evaluated beancount to organize my finances. As
recommended at the time I used v2. Made some good progress but my
project fell to the wayside.
Now I'm giving it another shot, and wondering if I should use v2 or v3?
Super cool. I should try to update my world a little and see how much I can
take advantage of v3 ( out of personal interest ). Thanks for the anecdata
Ben.
Alan
On Tue, 8 Feb 2022 at 19:06, Ben Blount wrote:
> Fava, importers, and beancount-import all work fine with v3 and I
> personally use
Fava, importers, and beancount-import all work fine with v3 and I
personally use all 3 with v3. I do recall some very minor patching being
required at one point, primarily to update import names. As you've said by
far the biggest change is in the importer structure.
On Tue, Feb 8, 2022 at 5:33 AM
My understanding is (I'm on v2) is that v3 is syntax-compatible with v2 so
the penalty (if there is one) for starting with V2 would be small. The
areas where there are clear gaps (to my mind) are:
- web frontend - AFAICT Fava is Beancount v2 only.
- importers have changed substantially
