Closed phil-mitchell closed 7 years ago
It looks like there is a problem with the ledger-python interface. ledger-autosync can interact with ledger, hledger, or the ledger python bindings. It will prefer python if available.
I myself don't often use the python bindings because I have found them to be buggy. I can reproduce this with my debian testing machine and will attempt to fix.
It will also add an option to disable using the python bindings so a user can at least work around these situations.
In the meantime, another workaround would be to remove the python ledger bindings or create a virtualenv that does not use them. If the bindings are not available ledger-autosync will not use them
Thanks for the quick reply. Removing ledger-python package resolves the issue for me. Glad to hear you can reproduce locally.
I have fixed the python binding tests and disabled their use by default.
Using master, the following command:
ledger-autosync -l test.ledger
Where test.ledger contains any transactions, e.g.:
Yields the following error if there were downloaded transactions that need to be processed: