I use bean-price / beancount.prices a lot (except the price sources) and 
interested in maintaining it. Though I'd rather maintain fork of the entire 
v2 codebase, because I don't see any reason to switch to v3.

On Monday, July 6, 2020 at 6:04:31 AM UTC+3, Martin Blais 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 beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/86c0868f-82ff-46fc-bb06-08fea0af85fao%40googlegroups.com.

Reply via email to