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 typing import TYPE_CHECKING

 from beancount.core.data import Entries
-from beancount.ingest import cache  # type: ignore
-from beancount.ingest import extract
-from beancount.ingest import identify
+from beangulp import cache  # type: ignore
+from beangulp import extract
+from beangulp import identify

 from fava.core.module_base import FavaModule
 from fava.helpers import BeancountError
diff --git a/tests/data/import.config b/tests/data/import.config
index a3b7353e..7c9b2f10 100644
--- a/tests/data/import.config
+++ b/tests/data/import.config
@@ -6,7 +6,7 @@ from dateutil.parser import parse
 from beancount.core.number import D
 from beancount.core import data
 from beancount.core import amount
-from beancount.ingest import importer
+from beangulp import importer



On Thu, Apr 7, 2022 at 11:07 AM [email protected] <[email protected]>
wrote:

> 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 [email protected] wrote:
>
>> 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 Alan H <[email protected]> wrote:
>>
>>> 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
>>>    - some third party systems might not yet support v3
>>>    (beancount-import comes to mind - upon which I rely heavily).
>>>
>>> Pivoting this to the positive; I'd love to hear from folks using v3 and
>>> what they use for 'favs-like' reporting / browsing and how they manage
>>> imports.
>>> I might be missing a trick here where you can switch between v2 and v3
>>> seamlessly (for example) and still do reporting using a v2 env and select
>>> what you want from v3.?
>>>
>>> Anyone using V3 (and V2?) feel like commenting?
>>>
>>> Thanks
>>> Alan
>>>
>>>
>>> On Tuesday, February 8, 2022 at 11:33:38 AM UTC 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?  Getting all my financial info together is a fair bit of work, and I'd
>>>> rather not change it all if v3 becomes "official" later this year.
>>>>
>>>> FWIW I'm a software developer, so if v3 requires use of git, C++
>>>> compilers, etc., that's not an issue.  But if it's unstable then I'd rather
>>>> move ahead with v2.
>>>>
>>>> Thanks for such a great tool.
>>>>
>>>> -- Colin
>>>>
>>> --
>>> 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/355eb4cb-0189-4679-af63-d10725289578n%40googlegroups.com
>>> <https://groups.google.com/d/msgid/beancount/355eb4cb-0189-4679-af63-d10725289578n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>> --
> 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/259649fa-d8f4-4626-a39c-0bc9f0a2d258n%40googlegroups.com
> <https://groups.google.com/d/msgid/beancount/259649fa-d8f4-4626-a39c-0bc9f0a2d258n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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/CACGEkZvNObzmR6kYFHSYm_h1z-G2TYdRk%3D2j6xSYKSbe8uSKmw%40mail.gmail.com.

Reply via email to