One possible issue I see is that any modification done by on_x_instance events on the base object would be lost once we overwrite the base object with the stub one 🤔 In this case the users can always use on_x events instead, which would happen after the base object was overwritten by the stub one. This will need a note in the docs, probably. And keeping a DEBUG log message would probably be useful too. Other than that, I think we can go ahead and do the change 🙂

I can deal with the docs update. Could you add back a DEBUG log message informing users that the object is overwritten by its stub equivalent?

Is this acceptable? The previous version had obj_member.kind.value and I'm unclear on whether the .value is necessary here on the .name calls.

                if obj_member.kind is not stub_member.kind:
                    # If the stub and the target are not of the same kind, prefer the
                    # stub over the target.
                    logger.debug(
                        "In %s, %s source object type != %s stub object type; "
                        "source object will be overwritten by stub object.",
                        obj_member.path,
                        obj_member.name,
                        stub_member.name,
                    )
                    obj.set_member(stub_member.name, stub_member)

Thanks! I think we can shorten it to "source object `%s` will be overwritten by stub object.", where %s is obj_member.path.