On Sun, Jul 12, 2020 at 5:35 PM Chary Chary <chary...@gmail.com> wrote:
> Sounds very exiting! > > For me the fact, that considerations are given to welcome a broader > community collaboration is a very positive sign, as I think it gives people > more confidence in the future sustainability of the product. > I'm more concerned about being able to actually respond to most tickets, so I need less stuff to maintain. Practical question about beancount query: > > You write that you envisage that most of the future users of it will be > outside of beancount. > > I thought the the reason beancount query was created is because it was > difficult to construct SQL query for beancount data. > The main reason the tool exists, is to fill in the gaps for things you can't easily do with just a table. In particular, you need a custom type for positions with an optional cost basis, and an aggregation rule for those, and a way to split up the units and currency to separate columns. Then there's the bells and whistles: the ability to clip a time period (open and close), a balance column, and a bottom line,. > > So, my question is: what will the future beancount query tool offer for > users outside of beancount, what they do not get now in Pandas of SQL? > That tool will become a tool that can process any table data, from various sources. It'll automatically infer schemas (by sniffing the data), and support the kinds of interfaces that are useful for Beancount (e.g. Google Sheets). It'll be less powerful and less efficient than something like Pandas (it'll process row-by-row, not columnar) but it should be more automatic. I think that the "one liner" nature of it will find broad usage. You should be aebl to process and join CSV files as if they were databases, for instance. On Saturday, July 4, 2020 at 8:34:50 AM UTC+2, Martin Blais wrote: >> >> Hi, >> Today I'm starting development on Beancount v3. >> >> This is going to be a pretty big change and will take a while. >> I've laid down the details in this document: >> >> https://docs.google.com/document/d/1qPdNXaz5zuDQ8M9uoZFyyFis7hA0G55BEfhWhrVBsfc/ >> <https://docs.google.com/document/d/1qPdNXaz5zuDQ8M9uoZFyyFis7hA0G55BEfhWhrVBsfc/edit#> >> >> This file describes the new set of dependencies for it: >> >> https://docs.google.com/document/d/10R-msZljuqFY8nckUnR1jVxMX1ol7rJUCMZo7w7QUQs/ >> <https://docs.google.com/document/d/10R-msZljuqFY8nckUnR1jVxMX1ol7rJUCMZo7w7QUQs/edit#> >> >> And there is a dedicated installation file for the in-development version: >> >> https://docs.google.com/document/d/1WwZYqsp28Uuk5eFqHQ1u1zqdjghymy8S_Yo-OJENoa4/ >> <https://docs.google.com/document/d/1WwZYqsp28Uuk5eFqHQ1u1zqdjghymy8S_Yo-OJENoa4/edit#> >> >> The short version is that v3's core is going to be ported to C++ using a >> Bazel build, and the codebase will be sectioned between core and the rest. >> I just merged the new build definition in master. >> >> The current head will be branched as "v2" and maintained stable. >> It will build with both setup.py and Bazel. >> Backward compatible fixes to it will be done there and merged into v3. >> v3 development will occur on branch "master" and breaking changes will >> occur there. >> >> Comments appreciated (on the docs, or here if you prefer), >> >> -- > 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/0d40115b-021c-4b5a-9172-641408c83644o%40googlegroups.com > <https://groups.google.com/d/msgid/beancount/0d40115b-021c-4b5a-9172-641408c83644o%40googlegroups.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/CAK21%2BhOzobFHe5SausPGgQkthifS3KfKqmHWbSVJssNyHFPqTA%40mail.gmail.com.
