2009/2/11 Stephan Richter <srich...@cosmos.phy.tufts.edu>: > 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.
Yeah, and so we're able not to deal with that in z3c.form itself and not to delay the release. Though I'd like this things to be done by someone who actually works with Zope2/Plone + z3c.form. Anyone? -- WBR, Dan Korostelev _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org 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 )
