Rewriting a 20-year-old Python library

> providing both sync and async code paths in the same class, often using a naming scheme which prefixes the async versions of the methods with an a

I have a solution to write a single code path for both async and sync

https://news.ycombinator.com/item?id=43982570

Brings back memories if when b-list was on the front page of HN all the time.

Another approach to preserve the fully functional api is decorators.

The binary "is spam" thing seems like a non-issue, unless I'm misunderstanding something. In Python you can easily implement Boolean attributes using predicates without breaking the API, like so:

    @property
    def is_spam(self) -> bool:
       return self._comment_check in {"true", "blatant"}

    @property
    def is_blatant_spam(self) -> bool:
       return self._comment_check == "blatant"

[dead]