On Thu, Feb 11, 2021 at 4:53 PM kuba....@gmail.com <kuba.ja...@gmail.com> wrote:
> Regarding importer development on v2, if I was to make changes to csv.py, > will the changes be migrated from the v2 branch into beangulp? I don't think a whole lot of development will happen on v2 anymore, especially for ingest and beanprice which have migrated out. Consider v2 frozen. I would suggest to please send a CL to beangulp for that. > I'm still unsure of how to use beangulp and I would like to make changes > to the importers so will I need to port the changes over myself once I > familiarise myself with the new world? > It'll be really quite similar, we're not adding a whole lot of new features, but rather making things simpler that should have been simple in the first place, learning from the lessons of having had to build a bunch of importers and working with them. We'll update the examples in the beangulp repo, don't worry. 99% of your code will be directly usable (all the hard parts anyway). Did I share the doc? Here are the changes: https://docs.google.com/document/d/1O42HgYQBQEna6YpobTqszSgTGnbRX7RdjmzR2xumfjs/edit dnicolodi@'s been doing great work and developing these changes and I'm looking forward to try it out and convert all my importers. If you have any ideas for how to make it better, please add them to the doc, Kind regards, > Kuba > > On Tuesday, 2 February 2021 at 13:07:40 UTC bl...@furius.ca wrote: > >> I have both and switch and git checkout and rebuild back and forth. >> Requires PYTHONPATH and local repos, not installed >> >> Beangulp will be sync'ed to master/v3 and if something it depends on >> changes in beancount and you're running it on top of a v2 install it might >> break so at some point compatibility may break. >> >> Beangulp/beangrow/beanlabs and other repos are all assumed to work only >> with v3 like that. It's the new world. Beanprice is an exception: it's >> only dependent on beancount at the edges (for output syntax, for optional >> extracting lists of currencies from the ledger, it barely needs a few >> imports, and will be decoupled, beancount dependencies isolated, i.e. a >> hledger user without a beancount install should be able to use it) and >> Kirill wants support for both v2 and v3. >> >> Why not find a way to have two setups? >> >> You could run your v2 installed with virtualenv, and your v3 setup like >> me from clones. That should work. FWIW, right now v3 still runs fine >> without the new compilation, the new c++ code is incomplete and not hooked >> up yet, it's living on the side in the ccore and cparser directories on >> branch master. At some point it'll switch over and it'll require a big fat >> bazel build to do anything at all but we're not close to that yet. Also, >> there will be a switchover to a public API as well at some point (all code >> outside the beancount repo will use a single import just like numpy, and >> that probably will break any circumstancial compatibility with v2 for >> projects that migrate to that api). >> >> >> >> >> On Tue, Feb 2, 2021, 01:28 Martin Michlmayr <t...@cyrius.com> wrote: >> >>> * Martin Blais <bl...@furius.ca> [2021-02-02 01:20]: >>> > - Nothing changed in v2, everything is still there. >>> > If you want things stable, stick with v2. >>> >>> Since beangulp creates transactions on stdout, is it possible to >>> migrate from ingest to beangulp while staying on v2 for other >>> functionality? (or is that not possible because beancount v2 >>> and v3 can't be installed at the same time?) >>> >>> -- >>> 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/20210202062819.GE2765%40jirafa.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+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beancount/52473f54-1870-4906-a639-45ddcdb5add3n%40googlegroups.com > <https://groups.google.com/d/msgid/beancount/52473f54-1870-4906-a639-45ddcdb5add3n%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%2BhM25o%2B9Sz%2BgzqS4CSP9KvA_FSCff2Y9o2dbCm6_716Nzg%40mail.gmail.com.
