explicit re-export from a private module should make the member public about pdoc

[mhils]

This feels more like a hack than anything else, but given that it's in PEP 484 I'd be happy to merge a PR that adds support for it. Fwiw, a strict reading of the spec seems to imply this only applies to stub files of I'm not mistaken...

As a workaround, I'd recommend to just declare __all__.

[DetachHead]

This feels more like a hack than anything else

tell me about it, that's python typing for you lol

a strict reading of the spec seems to imply this only applies to stub files of I'm not mistaken...

yeah i don't know why but for some reason most of the documentation and discussions around python typing seems to imply that you'd only ever use types in stubs and not actual source code. but the two main type checkers support this explicit re-export "syntax" outside of stubs (mypy and pyright) so i think it's safe to assume this behavior is intended to work in regular source code too

As a workaround, I'd recommend to just declare __all__.

thanks. though i'm not really a fan of __all__ since it would mean i have to add everything else in my module to it, and i prefer declaring whether something is public/private on its definition rather than in a separate section of the module. so the workaround i went with was to just import it and assign it to another variable:

# foo/public_module.py
from _private_module import foo as _foo

foo = _foo
"""the downside is that i have to move the docstring here tho"""