Hi,
As discussed prior on this mailing-list, bean-price has now moved away from
the beancount repository to a new repository under the same umbrella
organization:

https://github.com/beancount/beanprice

The code has been removed from beancount/master, yet it lingers in
beancount/v2 (where the plan is to minimize disruption).
All new tickets related to bean-price will be redirected to this new
repository; existing tickets in Beancount will be migrated.

New price sources are welcome into the new repo. Barrier to entry is a bit
lower (since I'm not planning to do all the maintenance work myself),
basically if you can write unit tests for a new price source that call both
the latest and historical functions (without actually making requests to
the network), compliant with the API and the style guide, your new price
source is likely welcome, send a PR. This may be a good time to consolidate
some of your custom price sources into one place if you want.

Note that in terms of code dependencies bean-price still depends on
beancount.ops.find_prices, where routines to enumerate commodities for
price enumeration remain. I plan to keep maintaining code the enumerates
prices required from a Beancount ledger there, as they are purely
processing Beancount directives. If they need to be extended for
bean-price, patches are welcome. I'm not too sure how importing from the v3
Bazel build will work yet, but I've kept the BUILD files for now, as they
will perhaps become necessary when the C++ build becomes the norm there.

Note that the new beanprice repo could be extended to work for Ledger and
HLedger as well; after all, the output is just text to be inserted in one's
ledger file, and only a change of output syntax.

-- 
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/CAK21%2BhO98B71fjdp6RmH5z2e9-aSGntrJjnzceSesEkavavurA%40mail.gmail.com.

Reply via email to