> Sorry this page is totally outdated, I will correct it. > The place to report telepathy-python bugs is in the freedesktop > bugzilla, product Telepathy in component tp-python : > https://bugs.freedesktop.org/enter_bug.cgi?product=Telepathy&component=tp-python
Thanks, now filed https://bugs.freedesktop.org/show_bug.cgi?id=26059 > You should never have to copy the bindings in your own repository, > instead use proper subclassifications. I'm not copying everything, just the mixins. My users expect me to support Maemo 4.1 and Maemo 5 which run telepathy-python 0.15.7 and 0.15.13, releases that saw breaking changes inbetween them for CM implementers. I was originally trying to support both packages and use their mixins but there was enough coupling between internals of each class I gave up on that. I actually find the mixins setup a bit weird. The "publicly" available bindings (not counting things in _generated) are a mix of mixins and interfaces. I think it'd be helpful to expose publicly all the interfaces and provide separately the mixins and clearly distinguish them. This way as someone upgrades, what they thought was just an interface doesn't surprisingly become a mixin. It'd also be helpful to make the binding points clear like each mixin provides an abstract property or function for what it needs to talk to. It was kind of surprising to see ConnectionInterfaceRequests expect the Connection to have the Channel Manager named self._channel_manager. I used this approach to make the dependencies in relationships clear in reaction to some frustration in figuring out how telepathy-python and telepathy-butterfly worked. If there is interest in these changes, I'd be willing to help implement it. I know, I'm a horrible person. I'm complaining about breaking changes and encouraging more breakages ;) Ed Page _______________________________________________ telepathy mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/telepathy
