qifparse
qifparse copied to clipboard
giacomos
qifparse is an incredibly useful project and its overall design is easy to understand and hack on. But we have one problem: the project seems to no longer be maintained....
…s only, additional fields and types are included. In particular, Option:AutoSwitch is described here: https://community.quicken.com/discussion/7147335/explain-the-qif-format-for-autoswitch A new test is added to ensure correct handling. Additionally: * Quicken 2013 can include...
A quicken 2016 export with transactions greater than 1000 will export it as 1,000. Parsing throws an exception when encountering this.
Date format can be 'DMY', 'MDY' or 'YMD' (defined in __init__). The date format is propagated to all parsers and the format is used to read QIF files (not only...
The code contains a check for !Type:Ccard, however the spec and my export use !Type:CCard. This errors since qifparse's check for this type is case sensitive.
I ran into difficulties with QIF files exported by an old version of Quicken. Some of the numbers had embeded commas (for thousands separators) and the date as in DD/MM'YY...
In parser.py, the day and month are incorrect. It should read like this: ``` if len(qdate) == 10: # new form with YYYY date iso_date = qdate[6:10] + "-" +...
I have some old memorized transactions that are not active, but still appear in the export. One of the accounts that was originally attached to one of the split lines...