[Zope-dev] Simplifying dependencies of zope.app.publisher

[Jim Fulton]

On Thu, Aug 6, 2009 at 4:39 PM, Shane Hathaway<shane at hathawaymix.org> wrote:
...
> I'm hoping Jim will soon take charge of zope.publisher, zope.traversing,
> zope.container, and zope.app.publisher, because he seems to be the only one
> who knows how they are supposed to be related.

Hah. Thanks a lot. ;)

Things have moved around so much over the last couple of years I'm not
sure anyone knows where things belong any more. ;)

I do have some ideas for some specific minor cleanups in some of
these. (That had to do with zope.app.publication, not
zope.app.publisher.)  That was blocked by the general instability we
have right now.  I'd really like us to stop moving things around until
we get to a point where we have a reasonable kgs that has tests
passing in Python 2.4-2.6 and on at least linux and mac.  Once we have
that and the processes in place to keep it, we can start to make
progress again.

I also have some ideas about how people should use zope.publisher (see
the in progress, though stalled, zc.publication). Again, once we reach
some stability, I can make progress on that again.

> For example, which packages
> should be aware of XML-RPC?  I would guess that none of them should have any
> notion of XML-RPC, and that there should be a "zope.xmlrpc" package, but my
> confidence in that guess is very low.

I'd really like to deprecate our current approach to XMLRPC. It's way
too complicated. In the mean time, I'd like to find ways to make it
more optional than it is now.

Jim

-- 
Jim Fulton