Hmm.. you’re right. There doesn’t seem to be an escape hatch for this. I think this is the relevant docstring from the python backend rule `get_exporting_owner`:

“”"Find the exported target that owns the given target (and therefore exports it).

The owner of T (i.e., the exported target in whose artifact T’s code is published) is:

1. An exported target that depends on T (or is T itself).

2. Is T’s closest filesystem ancestor among those satisfying 1.

If there are multiple such exported targets at the same degree of ancestry, the ownership

is ambiguous and an error is raised. If there is no exported target that depends on T

and is its ancestor, then there is no owner and an error is raised.

“”"