2009/3/13 Dan Korostelev <nad...@gmail.com>:
> 2009/3/11 Martijn Faassen <faas...@startifact.com>:
>>>>> - Move LocalPermission into new zope.localpermission package. I
>>>>> personally didn't ever need local permissions.
>>>> You're talking about locally defined permissions, correct, not about
>>>> giving someone a permission locally?
>>> I'm talking about local persistent permissions that can be added to
>>> ZODB and registered per site. It's zope.securitypolicy that gives
>>> local permissions, so, LocalPermission has nothing to do with local
>> Right, that's what I thought. Agreed they should go off into a package
>> on its own, probably to eventually die. :) (I have bad memories of
>> struggling with this stuff in a sprint in 2003).
> Thinking now. If we want local persistent permissions to be considered
> dead and we want to discourage their usage, may be the package should
> be called "zope.app.localpermission" then? If so, we could also move
> its ZMI views there and forget about that package. :) It's just
> because "zope.localpermission" name sounds like "some nice part of
> zope framework", but in reality, the functionality provided by the
> package is deprecated for use withing _the framework_.
> But, do we really want it deprecated and dead? May be there's some
> nice use cases for it? Anyone?
Martijn, Stephan, anyone? This question is the only thing that stops
me from releasing refactored packages.
Personally, I quite like the idea of naming it
"zope.app.localpermission", merging it with its views (possibly as an
optional dependency) and forgetting about it. But it's just because I
didn't ever need and probably won't ever need local permissions, so
it's one of some "old and deprecated patterns" to me.
So, if noone will object/reply soon, I'll rename the package and
finally release the refactorings.
WBR, Dan Korostelev
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -