Thank you both, Martin for the beangulp documentation and Dan for the clear instructions.
As a result I've managed to convert one of my scripts quite easily. However on running the extract command, I am immediately hit with an issue with the rounding of the amount. What used to be in v2 2020-12-29 * "INTEREST PAID AFTER TAX 0.00 DEDUCTED, 7.69" Assets:Current:S 7.69 GBP is now 2020-12-29 * "INTEREST PAID AFTER TAX 0.00 DEDUCTED, 7.69" Assets:Current:S 7.69000000000000039079850466805510222911834716796875 GBP I think beangulp is quite neat but I have some concerns around its day to day use but perhaps that is because I have not been using it properly yet. I have all my importers in their own git repos, most of which are not production ready and so are not on pypi. I guess in fact most peoples importers may be so specific to their needs that they would not be put on pypi either. So in world where we all have multiple importers in development, would the recommendation be a) to install the importers into the venv of beangulp or b) to create a venv for each importer and install beangulp into each or c) some other option? a) Is easier to use because one would not need to switch venvs while importing. b) Protects against package issues between importers. c) Perhaps it's enough to add my importers to the PYTHON_PATH and hope for the best. Kind regards, Kuba. On Thursday, 11 February 2021 at 23:26:51 UTC+1 [email protected] wrote: > On 11/02/2021 22:53, [email protected] 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'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? > > Hello Kuba, > > currently the v2 codebase is in maintenance mode: only bug fixes and > changes that can be trivially merged into v3 are likely to be accepted. > This disqualifies most changes to the ingestion framework that are not > fixes for bugs affecting users. > > Also, if anything, I expect the CSV importer in beangulp to become > simpler, and not to gain new features. It was intended as an example to > demonstrate how to write an importer and grow into something with a know > for every aspect, and it deviated from its original scope. > > However, if you have some improvements in mind, we can discuss them case > by case. Please feel free to send PRs for beangulp. > > So far, the only thing that changed in bengulp is the command line > interface, thus all existing importers can be easily migrated to it by > simply fixing the imports. > > Installing beangulp should be easy: > > $ python -m venv gulp > $ cd gulp > $ ./bin/pip install git+https://github.com/beancount/beancount/ > $ ./bin/pip install git+https://github.com/beancount/beangulp/ > > or > > $ git checkout https://github.com/beancount/beangulp/ > $ cd beangulp > $ python -m venv . > $ ./bin/pip install git+https://github.com/beancount/beancount/ > $ ./bin/python setup.py develop > > if you want to hack on the code, or similar incantations. > > Cheers, > Dan > -- 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/b8f0474c-ee18-46b9-8952-ff56b9e08ddcn%40googlegroups.com.
