Dan Korostelev wrote:
> 2009/3/11 Martijn Faassen :
[snip]
>> If it doesn't introduce new dependencies, I think a few more definitions
>> of permissions in zope.security won't hurt (only those commonly used).
>> I'd like that better than introducing a new package. Do you think this
>> will be toler
2009/3/11 Martijn Faassen :
> Dan Korostelev wrote:
>> Originally, I wanted to only move the "zope.Public" permission
>> declaration into zope.security, because that permission name is
>> special and always available. As for other permissions
>> (zope.View/zope.Security/zope.ManageContent, etc.), I
Hey,
Dan Korostelev wrote:
> As a part of zope.app.security refactoring process, I extracted local
> (persistent) permissions to new "zope.localpermission". And I faced
> one problem and I'm not sure about its resolution.
>
> Originally, I wanted to only move the "zope.Public" permission
> declar
Hi people!
As a part of zope.app.security refactoring process, I extracted local
(persistent) permissions to new "zope.localpermission". And I faced
one problem and I'm not sure about its resolution.
Originally, I wanted to only move the "zope.Public" permission
declaration into zope.security, be
