Fixed (in v2).
https://github.com/beancount/beancount/commit/628acbfa42d6c0f3b2cd47bd0eae44b4f8b4b0db
On Sun, Dec 13, 2020 at 6:45 PM Martin Blais wrote:
> That's indeed not consistent behavior and ought to be fixed.
> I filed a ticket to look into it, ideally we'd want to get the same
>
That's indeed not consistent behavior and ought to be fixed.
I filed a ticket to look into it, ideally we'd want to get the same
behavior.
https://github.com/beancount/beancount/issues/588
On Tue, Dec 8, 2020 at 8:55 PM James Cook wrote:
> I've noticed that sometimes when plugin code triggers
On Wed, 9 Dec 2020 at 02:04, James Cook wrote:
> On Wed, 9 Dec 2020 at 01:59, James Cook wrote:
>
>> On Wed, 9 Dec 2020 at 01:55, James Cook wrote:
>>
>>> I've noticed that sometimes when plugin code triggers a runtime error, I
>>> don't get a stack trace. Here's a made-up minimal-ish example:
On Wed, 9 Dec 2020 at 01:59, James Cook wrote:
> On Wed, 9 Dec 2020 at 01:55, James Cook wrote:
>
>> I've noticed that sometimes when plugin code triggers a runtime error, I
>> don't get a stack trace. Here's a made-up minimal-ish example:
>>
>> from beancount.core import amount, data, number
On Wed, 9 Dec 2020 at 01:55, James Cook wrote:
> I've noticed that sometimes when plugin code triggers a runtime error, I
> don't get a stack trace. Here's a made-up minimal-ish example:
>
> from beancount.core import amount, data, number
> __plugins__ = ("foo",)
> def foo(entries, _options):
>
I've noticed that sometimes when plugin code triggers a runtime error, I
don't get a stack trace. Here's a made-up minimal-ish example:
from beancount.core import amount, data, number
__plugins__ = ("foo",)
def foo(entries, _options):
return [data.Transaction(
flag = "*",
