[Catalog-sig] [Distutils] packaging terminology confusion
mal at egenix.com
Thu Jan 7 22:51:43 CET 2010
Tarek Ziadé wrote:
> On Thu, Jan 7, 2010 at 10:29 PM, Brad Allen <bradallen137 at gmail.com> wrote:
>> On Thu, Jan 7, 2010 at 2:40 PM, P.J. Eby <pje at telecommunity.com> wrote:
>>>> As for projects: fine with me; PyPI would then be the Python Project
>> If this gets general agreement, there are probably some places where
>> the word 'package' should be replaced with the word 'project', right?
>> For example, should PEP-345 be retitled as "Metadata for Python
>> Software Projects 1.2" ?
> +1, we should reflect this terminology in all new PEPs and in
> Distutils doc as well
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.
OTOH, sets of components like Zope are indeed projects. However,
the number of PyPI packages which could reasonably be called a project
is relatively small and even those use Python packages to
separate their namespaces.
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