[Catalog-sig] [Distutils] packaging terminology confusion
mal at egenix.com
Thu Jan 7 23:12:47 CET 2010
Brad Allen wrote:
> On Thu, Jan 7, 2010 at 3:51 PM, M.-A. Lemburg <mal at egenix.com> wrote:
>> I don't think we need to change anything - most Python software
>> components come as Python packages nowadays, so the terminology
>> 'package' we've used all these years is correct.
> Do you mean only 'package' in the sense of an __init__.py container,
> or in the sense of a setup.py container? Both usages have been in use
> for years, but only the __init__.py package was formally recognized.
We have used the term 'package' for both a Python
software component as well as the Python module directories on
sys.path with a __init__.py marker.
I usually refer to the latter as 'Python package' and the former
What you download is a 'distribution file' which could be an exe,
a tarball, an egg, etc. There are many forms such a package
distribution can take and just as many ways to install them.
Once installed a 'package' usually creates a single 'Python package'
(at top-level or some lower level).
As a result, after installation there is little difference between
a Python software component called 'package' and the module
directory called 'Python package'. qed :-)
Professional Python Services directly from the Source (#1, Jan 07 2010)
>>> Python/Zope Consulting and Support ... http://www.egenix.com/
>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/
>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/
::: Try our new mxODBC.Connect Python Database Interface for free ! ::::
eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48
D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
Registered at Amtsgericht Duesseldorf: HRB 46611
More information about the Catalog-SIG