[Zope3-dev] Re: move 'App' out of 'Zope'

[Jeff Kowalczyk]

"Martijn Faassen" wrote
>   python
>     zc (was zope)
>       reusable packages
>     zope (was app)
>     zodb

If you'll pardon a few 'why is the sky blue'-level questions, which are specifically not
advocating their obvious theme:

- What are the differences between a reusable 'zc' package and an ordinary package
installed in the user's python site-packages using dist-utils?

- Which priorities are reflected in the consensus to the above question:
a) Zope setup ease
b) Zope development ease (debugging a convenient source code layout)
c) Ease of testing Zope with multiple python versions (2.2.x, 2.3 CVS)
d) Zope is runnable with cvs checkout, no post-steps required
e) Zope component discovery and registration ease
f) Import statement compactness and consistency
g) Ease of reuse for python packages in both Zope and general python programs
h) Broad audience for zc reusable components among general python users accustomed to
distutils support

- Does the Zope3 component configuration make it easy to treat python packages outside the
Zope file layout heirarchy as first-class Zope components?

- Assume the new Zope component architecture and configuration fosters growth in new
python components or the refactoring of existing components that offer specific
enhancements to Zope and are reusable to general python programs without modification
(XML, PDF and SVG Zope tools, network protocol libraries (Jabber, etc.), workflow engines,
data adapters, etc).
Should those new packages find homes in python site-packages or in 'zc'?