Hi,
Maybe a stupid question but, what do you want to put into the inline
comments? Maybe you can put them as metadata, that way it could even be
queryable if needed.
Regards,
Patrick
On 28.11.2020 20:09, Chary Chary wrote:
Martin,
is my understanding correct, that by following your example from
Ameritrade
<https://github.com/blais/ameritrade/blob/master/examples/ameritrade2beancount.py>one
cannot create a beancount file, which contains inline comments for
postings, like that?
*2015-01-01 * "Taxi home from concert in Brooklyn"
Assets:Cash -20 USD ; inline comment
Expenses:Taxi*
Reasons:
1. There seems to be no place for comment in the *Posting
<https://github.com/beancount/beancount/blob/38e14b8dcf47754cb21ae7e5aceb77efc4c11688/beancount/core/data.py#L177>*class
(only may be in meta-data?)
2. As far as I can see, printer.print_entries() cannot print posting
comment
If this is the case, what is the best way to create a custom script
for converting data into beancount format with possibility to preserve
inline comments for postings?
On Saturday, October 10, 2020 at 3:23:56 AM UTC+2 [email protected] wrote:
You can either write a custom script and just print out to stdout,
or use the ingest framework.
Here's an example of a custom standalone script that converts from
Ameritrade:
https://github.com/blais/ameritrade/blob/master/examples/ameritrade2beancount.py
<https://github.com/blais/ameritrade/blob/master/examples/ameritrade2beancount.py>
The ingest library only provides a framework to help you automate
some of the process of automatically identifying the files in your
downloads directory, run the extraction of transactions (that you
write) and file away the downloads. You don't necessarily have to
use it. http://furius.ca/beancount/doc/ingest
<http://furius.ca/beancount/doc/ingest>
Hope this helps,
On Fri, Oct 9, 2020 at 7:32 AM Sam Bragg <[email protected]> wrote:
Hi all,
I'm completely new to beancount, but I want to use it to
manage my trading/investing activities. I have already written
a library to download transactions from my broker's API, which
returns a list of dicts.
I have looked at the beancount documentation and I can't even
seem to get started. Many of the example importers given,
assume that one has a file which they wish to import, which in
my particular case is not relevant(?).
Here's the process as I envision it:
1. Get a given date's transactions from my broker, using the
library I made
2. Implement some logic to classify each transaction
(Account:[fees/PnL] etc.)
3. Append the new transactions as directives in my beancount file
All I am really seeking to know at the moment is how I would
even get started. Looking at beancount.ingest.importer - it
needs a FileMemo instance, but in this case I won't be reading
from a file - this is where most of my confusion is coming from.
Truly grateful for any response received. Thank you so much
for producing this awesome software!
Sam
--
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/c38aefcb-0af3-4591-9905-b5f8fcc79fcan%40googlegroups.com
<https://groups.google.com/d/msgid/beancount/c38aefcb-0af3-4591-9905-b5f8fcc79fcan%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]
<mailto:[email protected]>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/beancount/2a32d0fe-3fd0-4098-a092-83e94ce5fdeen%40googlegroups.com
<https://groups.google.com/d/msgid/beancount/2a32d0fe-3fd0-4098-a092-83e94ce5fdeen%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/b0d0fbda-9edb-2e24-dc0e-84d158c55e1d%40ch.tario.org.
