On Wednesday 11 February 2009, Dan Korostelev wrote: > Yeah. So one solution, as I said before is to release zope.sitecompat > egg that provides a "zope.site" module, but doesn't implement a site > implementation, but instead imports things from old zope.app.component > (as does the new zope.app.component reversely). The same thing could > be done for zope.browser. However, this is an ugly solution, so I hope > Zope2 will move to eggs completely soon, so we won't have to deal with > problems like that.
If that works, +1. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter" _______________________________________________ Zope-Dev maillist - [email protected] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
