Oh, fair enough. I had misread the GP comment as being about __init__ (constructor methods) rather than __init__.py, package re-export. I'd make a small and mo

Oh, fair enough. I had misread the GP comment as being about __init__ (constructor methods) rather than __init__.py, package re-export. I'd make a small and mostly pedantic exception to "nothing but re-exports in __init__.py" for cases where you have a module with data (non-Python) files adjacent to the code, but which doesn't need more than one Python file to define its module logic. No point to have a tiny __init__.py that re-exports from an adjacent somemodule.py in that case. But generally yes, you're right.