[issue26178] Python C-API: __all__ Creator

Devyn Johnson added the comment: Thanks, @skrah and @haypo . I never thought of it that way. I made "__all__" in my extensions because "__all__" was used in many Python scripts. Thanks for the alternative perspective. -- status: open -> closed ___ P

[issue26178] Python C-API: __all__ Creator

Stefan Krah added the comment: I agree, and that's pretty much what Guido said here, too: https://mail.python.org/pipermail/python-dev/2001-February/012591.html -- nosy: +skrah ___ Python tracker _

[issue26178] Python C-API: __all__ Creator

STINNER Victor added the comment: Seting __all__ is usually need to exclude some symbols from "from module import *". In Python, it's common to write public or private (name prefixed by "_") helper functions which are excluded from __all__. In C extensions, you have to explicitly expose a func

[issue26178] Python C-API: __all__ Creator

New submission from Devyn Johnson: When creating Python modules via th C-API, it would be wonderful if there were an easier and more efficient way of creating an "__all__" for the module. In my opinion, an API function should be made; i.e., something like PyALL("FUNC1", "FUNC2", ...) Current