New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reorganize tests so that the functional tests are also discovered and run #6
Conversation
The test failure under pypy seems, maybe, to be related to how the security proxy should allow access to the |
I would expect |
I would expect that, but I would be wrong. The example test now fails: In [10]: type(prox)
Out[10]: zope.security.proxy.ProxyPy
In [11]: unicode(prox)
---------------------------------------------------------------------------
ForbiddenAttribute Traceback (most recent call last)
<ipython-input-11-cb9aea809750> in <module>()
----> 1 unicode(prox)
//src/zope/security/proxy.pyc in _wrapper(self, *args, **kw)
30 wrapped = super(PyProxyBase, self).__getattribute__('_wrapped')
31 checker = super(PyProxyBase, self).__getattribute__('_checker')
---> 32 checker.check(wrapped, name)
33 res = meth(self, *args, **kw)
34 if not wrap_result:
//src/zope/security/checker.pyc in check(self, object, name)
266 if name != '__iter__' or hasattr(object, name):
267 __traceback_supplement__ = (TracebackSupplement, object)
--> 268 raise ForbiddenAttribute(name, object)
269
270 check_getattr = check # 'See IChecker'
ForbiddenAttribute: ('__unicode__', <__main__.CustomClass object at 0x10b6dd110>) I'll take a look. |
Thanks for your comment/assistance @jamadden ! |
The PyPy issues should be fixed by zopefoundation/zope.security#52 |
zope.security 4.2.2 has been released with the fix. |
The pin here can be removed once zopefoundation/groktoolkit#6 is merged. |
Thanks @jamadden for picking up the |
WIP