Chris McDonough wrote:
view, but this wouldn't work for non-URL lookups. So people who use
'methods' now will need to monkeypatch in hideous ways just like the
'methods' stuff does now, in which case why not leave it?
Am I right as reading this as someone else who feels why are we
Chris Withers wrote:
Chris McDonough wrote:
view, but this wouldn't work for non-URL lookups. So people who use
'methods' now will need to monkeypatch in hideous ways just like the
'methods' stuff does now, in which case why not leave it?
Am I right as reading this as someone else who feels
I am interested in volunteering, but I am somewhat lost.
And I say that even though I have been developing in Zope for years, and
reading this email list avidly for a year.
I think that I am going to go and buy and read the Zope 3 book. Beyond
that I do not know what to do.
The problem is
On Tue, Jun 13, 2006 at 11:15:12AM -0700, Christopher Lozinski wrote:
Maybe there is a trade show where all the key players show up once a year.
A lot of people come to pycon and the europython conference.
I think in the Plone world, at least there are the two key players, and
then the
On 14 Jun 2006, at 00:45, Chris McDonough wrote:
On Jun 13, 2006, at 4:13 PM, Florent Guillaume wrote:
Yes but the deprecation has been there for a while, and the third
party product developers have been ignoring the warning. Their loss.
You're right. This only because I haven't managed to
FWIW I patched EE's trunk on svn.zope.org.
Thanks.
Or we can just pretend we never deprecated 'methods', remove the
warning, and get on with it; no harm, no foul.
Then the framework never gets cleaned up.
So be it. This is really minor. Not deprecating it is the right
thing, and I
