I'm also thinking about staying on v2. It covers all my needs, I love that it is written in python and it seems that v3 will bring too many breaking changes.
I don't use the parts which were removed, but I think it is important to provide at least some support for their users. The idea of splitting beancount v2 into several packages (core, bean-report, bean-web, price sources etc) seems reasonable. These packages can be maintained separately by those who use them, and in the ideal scenario, some of these packages will eventually become compatible with both v2 and v3. On Monday, July 6, 2020 at 6:42:24 PM UTC+3, Daniel Clemente wrote: > > > Checkout branch "v2" if you really must have those right now. > > Let me know if you care for those, at this stage I could easily fork a > copy to a separate repository (for others to maintain). > > I still use bean-web from time to time, though I don't depend on it since > I have my own scripts to extract data. Having a user interface seems pretty > basic for a simple accounting software. fava isn't simple in my opinion. I > chose beancount because it's simple. > > The rewrite and the architecture changes in v3 may be needed to keep the > project interesting, but v2 is good for my needs, and I don't think my > accounting needs will change in a few decades, so I'll keep using v2. > Thanks for it. > > > On Mon, Jul 6, 2020 at 6:04 AM Martin Blais <bl...@furius.ca <javascript:>> > wrote: > >> Hi, >> A per >> https://docs.google.com/document/d/1qPdNXaz5zuDQ8M9uoZFyyFis7hA0G55BEfhWhrVBsfc/ >> >> <https://docs.google.com/document/d/1qPdNXaz5zuDQ8M9uoZFyyFis7hA0G55BEfhWhrVBsfc/edit?pli=1#>, >> >> I just deleted: >> - bean-web (use Fava) >> - bean-bake (unfortunately no replacement) >> - bean-report (use bean-query or Fava) >> Checkout branch "v2" if you really must have those right now. >> Let me know if you care for those, at this stage I could easily fork a >> copy to a separate repository (for others to maintain). >> >> BTW, does anyone use "bean-price"? >> I suspect many (most?) uses have their own scripts to pull down price >> updates as directives. >> >> beancount.prices.* contains a few things: >> 1. Some library functions to extract lists of commodities requiring a >> price at dates, from a Ledger; >> 2. Code that defines a syntax for a price source, and some flags (e.g. >> whether to invert the price); >> 3. A library of price sources / implementations. Currently supports Yahoo >> Finance, IEX, Quandl, Oanda, Coinbase; >> 4. A binary that binds all these things together (bean-price). >> Here: >> https://github.com/beancount/beancount/tree/master/beancount/prices >> >> I'm going to isolate (1) and move it and ensure it remains provided and >> tested by the Beancount v3 core. >> However, I'm contemplating forking out (2,3,4) to a separate "beanprice" >> repository within the org. >> It would make it easier for others to contribute and maintain more price >> sources. >> WDYT? >> Is anyone interested in adopting and maintaining bean-price? >> >> -- >> 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 bean...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/beancount/CAK21%2BhNZETzSG7_7_xBX2xq2zaztFz6NrY9iA97mSWufLczY-g%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/beancount/CAK21%2BhNZETzSG7_7_xBX2xq2zaztFz6NrY9iA97mSWufLczY-g%40mail.gmail.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 beancount+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/467ce8c7-19dc-46b5-8c3a-1a91ca7e14ddo%40googlegroups.com.
