On Fri, Jul 2, 2010 at 5:18 PM, Giorgio Borelli <[email protected]> wrote: > Hi, > > Il giorno 25/giu/2010, alle ore 13.02, Sean Gillies ha scritto: >> The only reason I've included zope.app.security in zgeo.geographer's >> ZCML is to define permissions for the georeferencing annotator >> >> http://trac.gispython.org/primagis/browser/zgeo.geographer/trunk/zgeo/geographer/configure.zcml#L13 >> >> No zope security package is imported anywhere in zgeo.geographer. >> Maybe there's a more compatible way to define the permissions and then >> we could drop inclusion of zope.security or zope.app.security in the >> ZCML? > > > I think it's the correct way to define the permissions for a class. > > In Zope 2.10.x the package zope.app.security included the definitions of the > permissions > Now those have been moved in zope.security package (see: > http://pypi.python.org/pypi/zope.security#id6 ) > > For this reason we need to include zope.security instead of zope.app.security > to make zgeo.geographer work with Zope 2.12.x
Understood. If we can't support both in code or ZCML, we'll need separate branches to support different versions of Zope, or maybe collective.geo goes on toward Plone 4 and zgeo remains for Plone 3? Cheers, -- Sean _______________________________________________ Community mailing list [email protected] http://lists.gispython.org/mailman/listinfo/community
