Martijn proposed this be undeprecated (http://mail.zope.org/pipermail/ zope3-dev/2005-December/016781.html) and others agreed, at least in part. AIUI, Martijn ended up not making any changes in Zope 3, but somehow changing Zope 2 in such a way as to work around his issue.

The deprecation certainly is a pain for those of us who have one template replacement that sometimes may be user entered (non-message ids) and sometimes may be automatically generated (message ids).


Also, 3.3 is upon us, and the deprecation message claims that the behavior will be gone in this release.

I would have time for simply removing the deprecation, not changing the behavior in any way.

What's the consensus?

Gary


_______________________________________________
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com

Reply via email to