You can use the return value of this method as a boolean if you don't

        care which account string is matched.

        An account is considered to be under itself:

          Account('Expenses:Tax').is_under('Expenses:Tax') # returns 'Expenses:Tax'

        To do a "strictly under" search, end your search strings with colons:

          Account('Expenses:Tax').is_under('Expenses:Tax:') # returns None

          Account('Expenses:Tax').is_under('Expenses:') # returns 'Expenses:'

        This method does check that all the account boundaries match:

          Account('Expenses:Tax').is_under('Exp') # returns None

        """

        for prefix in acct_seq:

            if self.startswith(prefix) and (

                prefix.endswith(self.SEP)

                or self == prefix

                or self[len(prefix)] == self.SEP

            ):

                return prefix

        return None

class Amount(bc_amount.Amount):

    """Beancount amount after processing

    Beancount's native Amount class declares number to be Optional[Decimal],

    because the number is None when Beancount first parses a posting that does

    not have an amount, because the user wants it to be automatically balanced.

    As part of the loading process, Beancount replaces those None numbers

    with the calculated amount, so it will always be a Decimal. This class

    overrides the type declaration accordingly, so the type checker knows

    that our code doesn't have to consider the possibility that number is

    None.

    """

    number: decimal.Decimal

    # beancount.core._Amount is the plain namedtuple.

    # beancore.core.Amount adds instance methods to it.

    # b.c.Amount.__New__ calls `b.c._Amount.__new__`, which confuses type

    # checking. See <https://github.com/python/mypy/issues/1279>.

    # It works fine if you use super(), which is better practice anyway.

    # So we override __new__ just to call _Amount.__new__ this way.

    def __new__(cls, number: decimal.Decimal, currency: str) -> 'Amount':

class Metadata(MutableMapping[MetaKey, MetaValue]):

    """Transaction or posting metadata

    This class wraps a Beancount metadata dictionary with additional methods

    for common parsing and query tasks.

    """

    __slots__ = ('meta',)

    def __init__(self, source: MutableMapping[MetaKey, MetaValue]) -> None:

        self.meta = source

    def __iter__(self) -> Iterator[MetaKey]:

        return iter(self.meta)

    def __len__(self) -> int:

        return len(self.meta)

    def __getitem__(self, key: MetaKey) -> MetaValue:

        return self.meta[key]

    def __setitem__(self, key: MetaKey, value: MetaValue) -> None:

        self.meta[key] = value

    def __delitem__(self, key: MetaKey) -> None:

        del self.meta[key]

    def get_links(self, key: MetaKey) -> Sequence[str]:

        try:

            value = self.meta[key]

        except KeyError:

            return ()

        if isinstance(value, str):

            return value.split()

        else:

            raise TypeError("{} metadata is a {}, not str".format(

                key, type(value).__name__,

            ))

class PostingMeta(Metadata):

    """Combined access to posting metadata with its parent transaction metadata

    This lets you access posting metadata through a single dict-like object.

    If you try to look up metadata that doesn't exist on the posting, it will

    look for the value in the parent transaction metadata instead.