7 Oct
2009
7 Oct
'09
12:49 a.m.
Martijn Faassen wrote:
We could investigate two options:
* just removing that code that remove proxies and sees what happens to significant Zope 3 code bases. Risky.
* alternatively, putting in an optional dependency on zope.security in zope.component. If zope.security proxy is importable, try removing the proxies, otherwise don't.
Please don't add new dependencies to zope.component. Even optional ones, IMHO. It makes it harder to re-use for others and more complex to understand. Many people (e.g. those wanting to use GAE) object to the C stuff in zope.security in particular. Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book