telepathy-python should have an example connection manager
Submitted by Dafydd Harries
Assigned to Telepathy bugs list
Description
What the summary says.
Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.
Our infrastructure migration is complete. Please remember to update your SSH remote to point to ssh.gitlab.freedesktop.org; SSH to the old hostname will time out. You should not see any problems apart from that. Please let us know if you do have any other issues.
added 5. Tp-Python bugzilla labels
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.