[skipping a lot of lines ...] Brad> called 'packages'.) The word 'project' is not a suitable Brad> replacement for the word 'package',
right, imho it is been never considered to be Brad> because 'project' is a higher level abstract container of Brad> releases, not a downloadable file containing a setup.py. I would rather thing of project as some sort of namespace/process/community than being a container. Well container and namespace are maybe the same thing here so we might have the same understanding after all. Here is mine: - *package* means a Python package, (directory intended to be on sys.path, with an __init__.py. We *never* mean a distributable or installable archive, except when “impedance matching” with folks who think in terms of operating system parcels. - *parcel* is such a distributable / installable archive: either in source form (an ’sdist’), or one of the binary forms (egg., etc.). Any parcel may contain multiple packages (or even no packages, in the case of standalone scripts). - *project* is the process / community which produces releases of a given set of software, identified by a name unique within PyPI’s namespace. PyPI manages metadata about projects (names, owners) and their releases. Every real project has at least one release. - *release* is a set of one or more parcels of a project, each sharing the same version. Some PyPI metadata is specific to a release, rather than a project. Every release has at least one parcel. - *installer* is an OS specific piece of software provides by some project which usually installs a Python interpreter and other general software in order to have some Python application installed from scratch. _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
