[Checkins]
SVN: grok/branches/philikon-methodgrokker/src/grok/tests/security/missing_permission_
Requiring a non-existent permission that's never actually
used (because i.e. it's shadowed)
Philipp von Weitershausen
philikon at philikon.de
Mon May 26 06:57:25 EDT 2008
Log message for revision 86964:
Requiring a non-existent permission that's never actually used (because i.e. it's shadowed)
no longer produces an error.
Changed:
U grok/branches/philikon-methodgrokker/src/grok/tests/security/missing_permission_json3.py
U grok/branches/philikon-methodgrokker/src/grok/tests/security/missing_permission_xmlrpc3.py
-=-
Modified: grok/branches/philikon-methodgrokker/src/grok/tests/security/missing_permission_json3.py
===================================================================
--- grok/branches/philikon-methodgrokker/src/grok/tests/security/missing_permission_json3.py 2008-05-26 10:55:20 UTC (rev 86963)
+++ grok/branches/philikon-methodgrokker/src/grok/tests/security/missing_permission_json3.py 2008-05-26 10:57:25 UTC (rev 86964)
@@ -1,12 +1,8 @@
"""
-Make sure we get an error for a missing permission even if that permission
-isn't actually used (as there are more specific permissions)::
+An undefined permission that's never used (because it's being shadowed
+by a method-level directive) doesn't raise an error:
>>> grok.testing.grok(__name__)
- Traceback (most recent call last):
- ...
- ConfigurationExecutionError: martian.error.GrokError: Undefined permission
- 'doesnt.exist' in ...
"""
Modified: grok/branches/philikon-methodgrokker/src/grok/tests/security/missing_permission_xmlrpc3.py
===================================================================
--- grok/branches/philikon-methodgrokker/src/grok/tests/security/missing_permission_xmlrpc3.py 2008-05-26 10:55:20 UTC (rev 86963)
+++ grok/branches/philikon-methodgrokker/src/grok/tests/security/missing_permission_xmlrpc3.py 2008-05-26 10:57:25 UTC (rev 86964)
@@ -1,13 +1,10 @@
"""
-A permission has to be defined first (using grok.Permission for example)
-before it can be used in grok.require() in an XMLRPC class. This is even the
-case for a default permission that is never used.
+A permission has to be defined first (using grok.Permission for
+example) before it can be used in grok.require() in an XMLRPC
+class. However, this is *not* the the case for a default permission
+that is never used.
>>> grok.testing.grok(__name__)
- Traceback (most recent call last):
- ...
- ConfigurationExecutionError: martian.error.GrokError: Undefined permission 'doesnt.exist' in <class 'grok.tests.security.missing_permission_xmlrpc3.MissingPermission'>. Use grok.Permission first.
- ...
"""
More information about the Checkins
mailing list