-----BEGIN PGP SIGNED MESSAGE-----
> zope.app.component and zope.app.container are no longer part of Zope 2
> trunk, but CMF currently has many imports from these two packages.
> All the code needed by CMF has been moved to new packages (zope.site,
> zope.browser, zope.container) that are part of Zope 2 trunk, but they
> are not part of Zope 2.11.
> 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
> 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.
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Zope-CMF maillist - Zope-CMF@lists.zope.org
See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests