Heya, I'm hitting this error in the beancount v2 C parser (quoting from
beancount/parser/tokens.c):
if (lines > LONG_STRING_LINES_MAX) {
PyErr_Format(PyExc_ValueError, "String too long (%d lines)", lines);
free(unescaped);
return NULL;
}
What's the reason for that test/check?
(Curiously enough, I'm hitting it only from within Fava, whereas
bean-check standalone does not complain about that, not sure why.)
In case you're curious, such a long string comes from a specification
for the validate plugin:
https://github.com/zacchiro/beancount-plugins-zack/blob/master/validate.py
Arguably, it could/should just go to a separate file, referenced from
the beancount ledger, which would make the string trivially short, but
meh, it still seems to be an arbitrary restriction in the parser. What
am I missing?
Cheers
PS No, I cannot just switch to v3 and make this goes away, as Fava is
still on v2.
--
Stefano Zacchiroli . [email protected] . https://upsilon.cc/zack _. ^ ._
Full professor of Computer Science o o o \/|V|\/
Télécom Paris, Polytechnic Institute of Paris o o o </> <\>
Co-founder & CTO Software Heritage o o o o /\|^|/\
https://twitter.com/zacchiro . https://mastodon.xyz/@zacchiro '" V "'
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/beancount/20230802094325.dyjm4gofe2vovxdx%40upsilon.cc.
