Re: [Opensync-devel] python warning: 'set' conflicts with a built-in name

[Chris F. <cd...@fo...>]

On Tue, Jun 05, 2012 at 07:29:58PM -0400, Chris Frey wrote:
> If MysteryFunction() does not exist, then I need to use a serious hack,
> and wrap the Error object in another struct, so that the OSyncError pointer
> can change at will.

I was unable to find the MysteryFunction, but I believe I avoided any
serious hackage.

I also fixed a leak in the Error object's get_child(), and used the same
technique in other places in the code.

For those interested, the changes are here, and included in binary-meta:

	http://repo.or.cz/w/opensync/opensync-cdf.git

- Chris