Feel like this is just the very visible exception, I can’t think of any other internal that turned into a community darling that has its own issue about being made public. Its docstring even has examples. I bet even if they do figure out a better official alternative, they’ll just update the docstring and keep it around a long time for backwards compatibility.
Very quick work! Am I right in assuming this is intended for the “public” modules, like Base or a package-named module? Because such modules could be using internals exported by internal submodules, so it seems like a bad idea to wrap those submodules.