Gary Poster wrote:
Have you ever written functional tests and been surprised that they get
security proxies around i18n Messages and MessageIDs in the tests, but
not in the server? I have. :-)
I'm not sure how often people encounter this, but I think I've heard
one other person describe
On 8/8/05, Philipp von Weitershausen [EMAIL PROTECTED] wrote:
For compatability reasons, zope.app.security._protections and the
protect() function inside (though empty) should probably still exist for
at least another release because people might be using it in their own
tests (even though
Fred Drake wrote:
On 8/8/05, Philipp von Weitershausen [EMAIL PROTECTED] wrote:
For compatability reasons, zope.app.security._protections and the
protect() function inside (though empty) should probably still exist for
at least another release because people might be using it in their own
tests
On 8/8/05, Gary Poster [EMAIL PROTECTED] wrote:
Right. As I perhaps only hinted in the proposal, it is impossible to
import _protections from zope.app.security, because of this in the
__init__:
import _protections
_protections.protect()
del _protections
Depends on how you spell the
On Aug 8, 2005, at 10:21 AM, Fred Drake wrote:
On 8/8/05, Gary Poster [EMAIL PROTECTED] wrote:
lol. eek. yuck. :-)
Yep. Not sure what the best way to avoid this would be, either.
I'm assuming you mean in Zope 3, rather than avoiding this
possibility in Python, which seems like
On 8/8/05, Gary Poster [EMAIL PROTECTED] wrote:
I'm assuming you mean in Zope 3, rather than avoiding this
possibility in Python, which seems like futile road.
Indeed, and in particular, I was referring to the import behavior
itself. Your solution avoids the import quirkiness altogether, so it
Fred Drake wrote:
On 8/8/05, Gary Poster [EMAIL PROTECTED] wrote:
lol. eek. yuck. :-)
Yep. Not sure what the best way to avoid this would be, either.
Make a fake zope.app.security._protections module in sys.__modules__ ?
(The solution to a yuck *can* be a super-yuck!)
Florent
--
