Tres Seaver wrote: > yuppie wrote: >> >> Possible solutions: >> ------------------- >> >> 1.) Make Zope >= 2.12 required for CMF 2.2 and change all imports. >> >> 2.) Make Zope < 2.13 required for CMF 2.2. >> >> 3.) Add zope.app.component and zope.app.container to CMF dependencies. >> >> 4.) Re-add zope.app.component and zope.app.container to Zope 2 trunk >> dependencies. >> >> 5.) Add a lot of try except imports and modify zcml files to make >> imports from both locations working. >> >> >> Any preferences or better ideas? > > I would change CMF 2.2 to import from the new locations, and require > Zope >= 2.12: I can see no benefit in trying to straddle with 2.11, and > Plone 4.0 is supposed to move to Zope 2.12 and CMF 2.2 this year.
Ok. I'm fine with that. If there are no objections I'll make 'Zope2 >= 2.12.0b3dev' required and remove obsolete BBB code. 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
