Hanno Schlichting wrote: > yuppie wrote: >> Questions: Is there a good reason why Plone doesn't register >> portal_setup as utility? Does the same reason apply to CMFDefault? Do we >> have to support registered and not registered portal_setup tools? > > The reason why we don't register the setup tool as an utility anymore, > is that too many import/export steps in-the-wild required the REQUEST to > be available.
Are there use cases where the REQUEST is required or is this 'just' a backwards compatibility issue? > In general we removed the tool as utility registrations for all tools > where a request was still required. We'd like to put those back only > after the request is really not used anymore i.e. after the code has > been adjusted - not force any code to be changed due to the utility > registration. How do you encourage people to adjust their import/export steps? People will write new steps that depend on REQUEST if there are no deprecation warnings. > I'd prefer the portal_setup tool utility registration to be removed again. I'm not sure if the import/export steps used by CMF are clean or if nobody recognized the issue because nobody runs import/export steps from a portal_setup tool that was looked up as utility. Maybe the issue just shows up in combination with portal_quickinstall? I don't like to remove CMF's portal_setup registration *if* CMF itself is not affected by this issue. Cheers, Yuppie _______________________________________________ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
