Adding a python extension creates the ExtensionProxy property, which is set to default in the addExtension method. This property belongs to the extension. The problem arises when a second python extension is added. In FC the extension gets set the property correctly in the addExtension method. However, now there are two ExtensionProxy' properties in the object, one for each extension. Accessing it will return only one, which from both is undefined, as internally it iterates a c++ map and uses the first it finds.
This leads to the FreeCAD bug, that you cannot change the extension proxy correctly for more than one extension.
This leads to the collaboration bug, that the extension proxy cannot be set for a second extension at all.
Adding a python extension creates the ExtensionProxy property, which is set to default in the addExtension method. This property belongs to the extension. The problem arises when a second python extension is added. In FC the extension gets set the property correctly in the addExtension method. However, now there are two ExtensionProxy' properties in the object, one for each extension. Accessing it will return only one, which from both is undefined, as internally it iterates a c++ map and uses the first it finds.
This leads to the FreeCAD bug, that you cannot change the extension proxy correctly for more than one extension.
This leads to the collaboration bug, that the extension proxy cannot be set for a second extension at all.