Cases where people will write exotic macros here and there that will probably continue break swig (without even considering the static binary dependency for the client)
The macro is not exotic and it was never a problem. The error was in using a macro without a proper include in pyindi-client.
Most of the problems with PyIndi are related to the work on the INDI Library to keep the interface in the future without rebuilding dependencies.
Also, high-level functions that facilitate the development process are implemented.
I am currently creating automatic builds for Linux / MacOS. If you like, I can add additional tests for pyindi-client.