Florent Guillaume wrote:
Paul Winkler wrote:
On Fri, Dec 02, 2005 at 04:12:01PM +0100, Jean-Marc Orliaguet wrote:
does zope2 do an access control based on acquisition for public
methods, that would be a waste of resources since the answer is
always yes, granted ?
Well, the thing is, the
Dario Lopez-Kästen wrote:
Florent Guillaume wrote:
Paul Winkler wrote:
On Fri, Dec 02, 2005 at 04:12:01PM +0100, Jean-Marc Orliaguet wrote:
does zope2 do an access control based on acquisition for public
methods, that would be a waste of resources since the answer is
always yes, granted
Jean-Marc Orliaguet wrote:
is it a typo, or did you mean:
a_class.security.setDefaultAccess('allow')
it is a type and I do mean a_class.security.setDefaultAccess('allow').
/dario
--
-- ---
Dario Lopez-Kästen, IT Systems
Dario Lopez-Kästen wrote:
Florent Guillaume wrote:
Paul Winkler wrote:
On Fri, Dec 02, 2005 at 04:12:01PM +0100, Jean-Marc Orliaguet wrote:
does zope2 do an access control based on acquisition for public
methods, that would be a waste of resources since the answer is
always yes, granted
Jean-Marc Orliaguet wrote:
that's because it does not seem to work with new-style python classes in
zope2.7
it works with:
class MyStuff:
instead of:
class MyStuff(object):
This is what you would have got:
File /opt/Zope-2.7/lib/python/AccessControl/SecurityInfo.py, line
165, in
On Fri, Dec 02, 2005 at 11:57:16PM +0100, Florent Guillaume wrote:
Paul Winkler wrote:
(snip)
Well, the thing is, the declaration that makes the method public
*has no effect* unless your class participates in acquisition.
That's not true. The objects of this class will be perfectly
Paul Winkler wrote:
On Fri, Dec 02, 2005 at 04:12:01PM +0100, Jean-Marc Orliaguet wrote:
does zope2 do an access control based on acquisition for public methods,
that would be a waste of resources since the answer is always yes,
granted ?
Well, the thing is, the declaration that makes the
