Goodbye bean-web, bean-bake, bean-report. What about bean-price?

[Martin Blais]

Hi,

A per https://docs.google.com/document/d/1qPdNXaz5zuDQ8M9uoZFyyFis7hA0G55BEfhWhrVBsfc/, 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?

[Daniele Nicolodi]

On 05/07/2020 21:04, Martin Blais wrote:
> Hi,
> A
> per https://docs.google.com/document/d/1qPdNXaz5zuDQ8M9uoZFyyFis7hA0G55BEfhWhrVBsfc/

> 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).

Do you mean move them to a separate repository and remove them from v2
too or move them to another repository for someone to maintain them
working in v3?

Cheers,
Dan

[Kirill Goncharov]

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.

[Daniel Clemente]

> 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.

--
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+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/CAK21%2BhNZETzSG7_7_xBX2xq2zaztFz6NrY9iA97mSWufLczY-g%40mail.gmail.com.

[Kirill Goncharov]

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.

To unsubscribe from this group and stop receiving emails from it, send an email to bean...@googlegroups.com.

[Martin Blais]

That's a great question. I meant the latter, wasn't intending on messing with v2 too much. 

Perhaps I should cut things up and move files in v2, without making any other changes.

[Martin Blais]

On Mon, Jul 6, 2020 at 3:15 AM Kirill Goncharov <kdgon...@gmail.com> wrote:

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.

v3 will take a while, but at some point I'll stop development on v2 entirely.

I think it might make sense for me to move bean-price to another repo in v2 and let that evolve as it may.

Let me tinker with that idea for a bit.

 

 

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/, 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+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/86c0868f-82ff-46fc-bb06-08fea0af85fao%40googlegroups.com.

[Martin Blais]

On Mon, Jul 6, 2020 at 2:04 PM Kirill Goncharov <kdgon...@gmail.com> wrote:

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.

Actually I don't expect that v3 will break much. Existing syntax and semantics will remain the same. Perhaps I wasn't clear about that in my design doc.

The query tool will, on the other hand, change a lot.

 

 

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.

I think that's possible.

To unsubscribe from this group and stop receiving emails from it, send an email to beancount+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/467ce8c7-19dc-46b5-8c3a-1a91ca7e14ddo%40googlegroups.com.

[Vivek Gani]

BTW, does anyone use "bean-price"?

I suspect many (most?) uses have their own scripts to pull down price updates as directives.

FWIW, while I've been rather inactive on using beancount lately, I was using bean-price and spent time trying to extend it to fetch an 'update' of prices over time.

Intent was to try and make bean-price a bit more accessible for one-liner use rather than people writing their own script.

https://github.com/beancount/beancount/tree/pr128_seltzered_beanpriceupdate .

https://bitbucket.org/blais/beancount/pull-requests/128/add-a-update-option-to-bean-price/diff

As far as overall usage, I'm generally a beancount/fava user (prefer less command-line interaction), so:

bean-web: never used,

bean-report: never used

bean-query: on occasion

bean-identify/extract/file: yes, think everyone still needs this.

[Jason Chu]

I have commodity lines in my beancount file and use bean-price to append prices whenever I feel like it. I'm curious why that doesn't work for other people and why they need their own scripts.

--

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+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/585e931d-b160-4896-9dce-2f938cec5bado%40googlegroups.com.

[Stefano Mihai Canta]

That is my exact workflow. I run bean-price daily.

To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/CAFFHUgueJkQPHLLV3YA6jepcx1av3D3QrPMA6bnLNL0xwt5_aw%40mail.gmail.com.

[Zhen Cheng]

Same here. A cron job runs bean-price daily, with customed price sources.

[Tilo Schwarz]

Same here, running bean-price manually from time to time.

Best Regards,

Tilo

--

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+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/fae48d95-cd12-4328-be55-444be54b5264o%40googlegroups.com.

[Martin Blais]

Thanks everyone, this is useful.

To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/CAKXy0dHYLpHfTNhqbK%3DuaE%2BhQZOMUAgzHddut%2BPxuutJcfT7ow%40mail.gmail.com.

[Martin Michlmayr]

* Martin Blais <bl...@furius.ca> [2020-07-05 23:04]:
> I just deleted:

> - bean-report (use bean-query or Fava)

I'm not sure that's a great idea. While bean-report was a second
class citizen compared to bean-query, it has some functionality
missing from bean-query, e.g. bean-report print

bean-report holdings is also pretty nice.

Is someone planning on maintaining bean-report for v3?

--
Martin Michlmayr
https://www.cyrius.com/

[kuba jamro]

A possible approach could be to get involved in replicating the missing functionality into fava rather than to maintaining it in bean-count?

[francois PEGORY]

Hello, 

I run currently a cron script with personalized sources.

So having it integrated is not the best thing according me , you need to run fava and I don't run fava or there are  a possibility to have a Cron script . 

Maybe just keep the tooling but remove the source ....

--

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+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/f1bb1cbb-fbe9-4a8a-9bf3-e22762b987e4o%40googlegroups.com.

[Martin Michlmayr]

* kuba jamro <kuba....@gmail.com> [2020-07-17 07:26]:

> A possible approach could be to get involved in replicating the missing
> functionality into fava rather than to maintaining it in bean-count?

Most of the functionality I'm interested in from bean-report is useful
on the command-line, e.g. bean-report print.

[Martin Blais]

On Fri, Jul 17, 2020 at 3:16 AM Martin Michlmayr <t...@cyrius.com> wrote:

* Martin Blais <bl...@furius.ca> [2020-07-05 23:04]:
> I just deleted:
> - bean-report (use bean-query or Fava)

I'm not sure that's a great idea.  While bean-report was a second
class citizen compared to bean-query, it has some functionality
missing from bean-query, e.g. bean-report print

"bean-query print" does the same.

bean-report holdings is also pretty nice.

- Use Fava

- Use the beancount.projects.export script and aggregate in a spreadsheet

- We can build custom aggregators for cost and market value that would work in the new SQL tool

 

Is someone planning on maintaining bean-report for v3?

I could move it to its own repo if someone cares enough to take it over.

--
Martin Michlmayr
https://www.cyrius.com/

--
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+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/20200717071629.GN23829%40jirafa.cyrius.com.

[Martin Blais]

On Fri, Jul 17, 2020 at 10:44 AM francois PEGORY <pfranc...@gmail.com> wrote:

Hello, 

I run currently a cron script with personalized sources.

So having it integrated is not the best thing according me , you need to run fava and I don't run fava or there are  a possibility to have a Cron script . 

Maybe just keep the tooling but remove the source ....

Not entirely sure which part you're referring to, I will guess you mean bean-price, and that will be moved to its own repository, you should be able to install that separately and use it as before. I don't want to delete bean-price, I just want it in a separate repo so other people can help out or even eventually own it completely.

Le ven. 17 juil. 2020 à 16:26, kuba jamro <kuba....@gmail.com> a écrit :

A possible approach could be to get involved in replicating the missing functionality into fava rather than to maintaining it in bean-count?

On Friday, 17 July 2020 08:16:39 UTC+1, Martin Michlmayr wrote:

* Martin Blais <bl...@furius.ca> [2020-07-05 23:04]:
> I just deleted:
> - bean-report (use bean-query or Fava)

I'm not sure that's a great idea.  While bean-report was a second
class citizen compared to bean-query, it has some functionality
missing from bean-query, e.g. bean-report print

bean-report holdings is also pretty nice.

Is someone planning on maintaining bean-report for v3?

--
Martin Michlmayr
https://www.cyrius.com/

--
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+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/f1bb1cbb-fbe9-4a8a-9bf3-e22762b987e4o%40googlegroups.com.

--
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+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/CALUWbLfLXNwMHE%3DQv6WEhhfu7r%2BeMrjWfL_pGfRrKCbCT_8-Zw%40mail.gmail.com.