On Apr 30, 2008, at 5:11 PM, firstname.lastname@example.org wrote:
I have a less disruptive counterproposal. How about just starting to refer to directories (or "folders", or zip entries) with '__init__.py' in them as "package modules"? A package is-a module anyway.
That's a good idea.
I belive a multi-word term here would be similarly more memorable and precise. A "package distribution" would include the more familiar term while still being specific, consistent with the old terminology, and correct. Using a qualifying word is probably a good idea in this context anyway. I usually say "debian package", "RPM", "MSI", or "tarball" unless I'm specifically talking about "packages for your platform",
That's a good one too.
almost always in the phrase, "please do not use distutils to do a system install of Twisted, use the specific package for your platform".
This is a tangent, but why do you give that advice? I typically give people the opposite advice on how to install Twisted.
I do, however, agree with Steve emphatically on your original proposal. Changing the terminology now will make billions upon billions of Python web pages, modules (c.f. twisted.python.modules.PythonModule.isPackage()) documents, and searchable message archives obsolete, not to mention that 90% of the community will probably ignore you and use the old terminology anyway, creating more confusion than it eliminates.
I suspect 90% of the community already uses my proposed terminology -- that was my original challenge to round up a Python programmer and find out.
But I agree that my proposal would contribute to confusion and disruption, and I like your counterproposals better, at least for now.
Directories, folders, or zip entries with __init__.py in them are "package modules", and Python packages are "package distributions".