For me, I've used Butterfly as an example.  The downside is it doesn't exercise all of telepathy-python and it shows.  I think a mock connection manager would serve well as an example and help in automated tests.  I've found the coverage from butterfly and hand tests to be ... lacking as I've developed my CM (See 26059 and 26289)

Also I think would be important is to make clear the various coupling points.  Friend (access of _channel_manager) and inheritance (the whole design) are dangerous ways to couple and their use within telepathy-python have bitten me.  I made abstract properties in each mixin that expressed a contract of what the mixin expected from other classes to help understand the coupling points when mimicing Butterfly.  This would be beneficial for both an example CM and TP-P

On a related note to that related note (ok, so I really should file a separate bug at this point) except for the fact that I randomly need a parent's "_*" variable to work around some issue, it would be good if TP-P used "__*" because I've run into name clashes causing mysterious bugs.

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-python/issues/2.