[Zope3-dev] Zope 3 Packages vs Python Packages

[Shane Hathaway]

Steve Alexander wrote:
> Chris Withers wrote:
>> Ugh! Is it only me who see's the potential for huge amounts of 
>> unnecessary confusion?! Python got Package first, why not call the 
>> Zope 3 things 'bundles'.
> 
> 
> Do we need a different name for Zope 3 Persistent Classes and Zope 3 
> Persistent Modules too? Perhaps 'db-behaviours' and 'db-code-containers'?
> 
> 
> I'm absolutely fine with Python having packages, modules and classes, 
> and with Zope 3 having persistent packages, persistent modules and 
> persistent classes.
> We expect the 'persistent' variants of these things to work a bit 
> differently to the standard python ones.

AFAIK, that's not in question.  Persistent Python packages will still be 
called packages.  But look at the Zope 3 UI.  Services and other 
components are in packages.  This is a new concept.  These new things 
can hold configurations, components, and persistent Python packages. 
"Bundle" seems like a reasonable alternative to package in this case.

Shane