On Sat, Jul 4, 2020 at 4:20 AM Kirill Goncharov <[email protected]> wrote:
> Hi, > > What is the scope of expected breaking changes and how difficult will it > be to migrate? I use beancount a lot and particularly interested in API > changes in core, prices, ingest, loader and query subpackages. > Syntax and semantics will very likely remain the same. API also likely to remain very close, but more of the code will be bound to Python from C++ (no guarantees, pybind11 may bring some challenges). In any case, the schema will have a similar shape and so it should be pretty straightforward to port existing code. The query tool will change a lot, and by that, I mean improve. It's also going to be rewritten from the ground up and be better tested, and also have types. Will beancount v3 be available on PyPI? It's not clear from the docs. > Not 100% sure, I'd like to; we'll have to figure out this detail later. In theory if we can build binaries, we should be able to package it. > On Saturday, July 4, 2020 at 9:34:50 AM UTC+3, 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beancount/3c333f25-0afa-4471-892e-4cb8aa368c6eo%40googlegroups.com > <https://groups.google.com/d/msgid/beancount/3c333f25-0afa-4471-892e-4cb8aa368c6eo%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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/CAK21%2BhPyG0cJ1y_A_%2B3LJeCUoHE42d8NRCbjOf3SUqUYCQdE-Q%40mail.gmail.com.
