[Zope-dev] Dependencies and future of zope 3

Philipp von Weitershausen philipp at weitershausen.de
Wed Sep 3 13:55:27 EDT 2008


Benji York wrote:
> On Wed, Sep 3, 2008 at 11:41 AM, Stephan Richter
> <srichter at cosmos.phy.tufts.edu> wrote:
> 
>> For several packages we took the following approach. Most packages that have
>> browser packages are in zope.app; for example, zope.app.folder (we did not
>> convert this package yet). We then took the API and moved it to zope.folder.
> 
> Maybe we should create a new namespace package for "browser" code.
> 
> How about "zope.browser"?

-0

My general sentiment is against creating more structure than we already 
have. Flat is better than nested. IMHO it's perfectly ok to have the 
Python APIs in zope.foo and browser code in zope.app.foo. I think sooner 
than later people won't want to the zope.app.* stuff anyway.



More information about the Zope-Dev mailing list