No problem. Just to be clear, your new importers should still work using
bean-extract. Your usage should remain identical - the only thing that will
change is the code that is used to do the extraction.
On Fri, Apr 5, 2019 at 10:06 AM Zhuoyun Wei wrote:
> Thanks. My current workflow is to use "b
Customize the class to make identify() match on file.name rather than the
content and create two instances with different account names.
On Thu, Apr 4, 2019, 04:33 Zhuoyun Wei wrote:
> Hi,
>
> the CSV importer determines the account to use by "regexps" parameter. I
> have two accounts from the s
Thanks. My current workflow is to use "bean-extract" to extract transactions
from multiple CSV files downloaded from different institutions. I have been
using this workflow for a few years, until recently I opened a savings account.
I will look into how to use the importer directly, instead of u
By the way, just wanted to note this is for extraction purposes since you
need to use a different account based on the file name. If it's only for
identification purposes, the identifier mixin already supports matching on
the file name (
https://bitbucket.org/blais/beancount/src/fa1edde3bcd02a277fa
You can't do it with the CSV importer the way it's currently written. You
will need to write your own importer.
Something like this, but obviously refactored in a nicer way.
def extract(self, file):
file_name = path.basename(file.name)
if file_name == "something.csv":
Hi,
the CSV importer determines the account to use by "regexps" parameter. I have
two accounts from the same bank (one checking and one savings), and the CSV
files of both are of the same format. There isn't anything in the file content
that could tell the two accounts apart. The only differenc
