New issue 169: Consider always creating some transaction object even when there are errors. https://bitbucket.org/blais/beancount/issues/169/consider-always-creating-some-transaction
Martin Blais: > Furthermore, attempting to debug with bean-doctor doesn't quite work for me. > The transaction in question starts at line 17. But beandoctor context > <filename> 17 returns the context for the previous transaction at line 13. That's interesting; if there's no error, it works fine. However, I think in this case, because this error was irrecoverable, the transaction was skipped, and the behavior of the line-number selection is to select the closest previous transaction. It does result in an odd behavior. Maybe I should always create transactions even when there are errors. This would require a fair amount of testing. It's not necessarily a bad idea. Responsible: blais -- 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 post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/20170616033428.17215.55644%40celery-worker-107.ash1.bb-inf.net. For more options, visit https://groups.google.com/d/optout.
