Difference between submodules and subpackages?

[dstansby]

I'm trying to use autoapi to document a package, and am getting the API docs grouped in both "submodules" and "subpackages":

Does anyone know

1. The difference between a submodule and a subpackage?
2. How I can group these together (ie. merge the lists above) so that all the second level API docs are in a single list, instead of spread across submodules and subpackages

[AWhetter]

A package is a directory that contains an __init__.py and may have packages or modules under it. A module is a .py file. There's no difference in usage to a user however so it's maybe a bit pedantic to separate them. I think we'll change this to lump everything under "submodules".

[zbentley]

+1 to merging them; I think many packages like to move things between "submodule" and "subpackages" as an internal implementation detail (e.g. when a submodule.py grows so much support code for its public exports that it needs to be split into submodule/__init__.py for public stuff and submodule/_internal.py for the rest).

[zbentley]

Terrific, thanks so much @AWhetter!

[austinzh]

A package is a directory that contains an __init__.py and may have packages or modules under it. A module is a .py file. There's no difference in usage to a user however so it's maybe a bit pedantic to separate them. I think we'll change this to lump everything under "submodules".

any update on this, or maybe a workaround to have only submodules?