yuppie wrote:
I believe the Hippocratic Oath should be followed in subjective cases
like this. "First, do no harm."
Cruft does harm. It discourages people who want to understand and
improve Zope. And it encourages people to stick to bad coding habits.
As far as "methods" goes, I call bullshit on this. Simple documentation
of what "methods" is used for probably would have sufficed...
Why do you want to have special support for monkey patching Folder?
Which use cases justify to pollute the Folder API in that way?
This is Zope 2, namespace polution is _not_ something that's going to
get fixed...
cheers,
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )