Reference to package as "module" is confusing

[Bob Kline]

Following up on the related ​forum discussion, I propose changing

... add the name of the module that contains your models.py.

to

... add the name of the package that contains your models module.

in the ​Using models section of the documentation.

In my experience, most Python programmers are not aware that, technically speaking, a package is a special type of module. This is due principally to the fact that most of the relevant language in the Python documentation implies that the term "modules" does not include packages. In the tutorial the application package is referred to as a "package," not a "module," and there is no reason not to use the more specific term here, preventing unnecessary confusion.

I will submit a PR shortly.

[Jacob Walls]

Hi Bob, thanks for the ticket. I saw this on forum and was going to reply. I don't think we want to describe the models module as a package, as it's not intended to be distributed by itself.

That sense of "package" as "packaged for distribution" is clarified here:
​https://docs.djangoproject.com/en/5.2/intro/reusable-apps/#reusability-matters

Given that startapp doesn't create any package metadata I'm wary of adopting that "package" wording in additional places. In other words, neither the models module nor the app needs to be a package.