-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 6 Jan 2007, at 15:34, Hanno Schlichting wrote:
I had to change two things in CMF so far though. Here are the
patches I
came up with:
Thanks Hanno, this is a point I wanted to bring up after getting the
last work done: When using getUtility/queryUtility, I am assuming the
returned utility should always considered to be unwrapped. Because
that's what the unit tests show me. There are several places where
CMF unit tests failed and I ended up manually wrapping the utility
where I retrieved it using __of__, but I'm not sure if I'm expected
to do it that way. It's clear that some tools must be wrapped in
order to perform their function - that's why for example the method I
wrote to replace getToolByName for untrusted code still expects a
context to be passed along and I wrap the utility in it.
It's just a bit unintuitive that sometimes you must wrap them,
sometimes you don't need to. For a third party coder this could turn
into a major headache and bug bear.
jens
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD4DBQFFn7eYRAx5nvEhZLIRAouMAJ4rDlUqxta4tkC0IGIDzk2INNeG5wCVHi6k
tGCzE5BwZhM7kJFx5pBB8Q==
=t6kR
-----END PGP SIGNATURE-----
_______________________________________________
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
