Daniele Nicolodi

The current data Beancount data model does not allow for list valued metadata entries. Metadata is stored in a dictionary and thus metadata keys cannot be repeated. I think that...

> Even then it automatically creating lists on the presence of multiple values would result in sometimes lists sometimes single objects, not super consistent. I agree, this is not ideal...

> > I agree, this is not ideal and gets messy to handle quickly. Although, there is no mechanism in place that asserts that metadata entries with the same key...

I am not familiar with the depreciation plugin, although I doubt implements this specific use case. I suggest you to modify it to implement what you need. The possibility to...

Limit the width of the output of which command exactly? And limit it how? Can you provide an example of this behavior applied to a beancount command?

The CI uses the `requirements.txt` file in the repo to install dependencies. However, `requirements.txt` is incomplete as it at least misses the dependency on `chardet`. So far we got `chardet`...

> All this seems unrelated to this PR Sure, I didn't want to imply that the fix had to be part of this PR. I'm sorry to have given you...

`bean-web` is dead for good but I think it can be resurrected outside Beancount core if someone is interested in maintaining it. One important issue with keeping `bean-web` alive is...

I don't think the results you report are incorrect, they simply use the wrong precision. Can you please elaborate on this aspect? Beancount and thus `bean-price` infer the reporting precision...

I haven't looked at the proposed patch in detail, but I think that maintaining the expansion of the unicode ranges in beancount is not ideal: it is hard to get...