I don't think this is going to work because of bzlmod visibility. rules_python only has visibility to the repos in its module.bazel, so if another repo is rendered into the generated code, it won't be visible.

I was, perhaps naively, thinking to have, quite literally, a single macro call in the generated code:

load("@rules_python//whatever.bzl", "define_pypi_package")

define_pypi_package(
  name = "foo",
  ...
)

Though admittedly, I hadn't thought through what all the args would be and if such a call wouldn't be overly complicated.

In any case, the idea behind doing it as one macro was to allow additional targets to be defined. The cases I had in mind were to define a cc_library or entry point.

A second reason for doing it this way to avoid having lots of symbols to override. Though, I suppose on advantage of naming the specific symbols to load is you can reduce how much is loaded.

Perhaps splitting the difference? Have a single macro per "type" of pypi package that gets defined. e.g., a wheel based package needs to load the define_pypi_package_from_wheel(...) symbol; an sdist-based package needs to load the define_pypi_from_sdist(...) symbol.

I'm feeling pretty -1 on the granularity in this PR, though, e.g. filegroup, py_library, etc. Those really seem like implementation details of "define a pypi package"