On 02/02/2021 07:28, Martin Michlmayr wrote: > * Martin Blais <[email protected]> [2021-02-02 01:20]: >> - Nothing changed in v2, everything is still there. >> If you want things stable, stick with v2. > > Since beangulp creates transactions on stdout, is it possible to > migrate from ingest to beangulp while staying on v2 for other > functionality? (or is that not possible because beancount v2 > and v3 can't be installed at the same time?)
Thinking about it, there is no reason for beangulp to require beancount v3, thus I could easily lower the minimum required beancount version for banngulp, if it makes life easier for someone. The main rationale for beangulp requiring beancount 3.0.dev0 is that in this version the old ingest framework is gone and thus it is easier to spot the imports that needs to be updated to the new location in the code using them, and it makes it impossible to mix imports from different locations, with possibly nasty bugs hard to diagnose. 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/848d801f-4474-5cc2-b0e9-0024be2ffddb%40grinta.net.
