-----BEGIN PGP SIGNED MESSAGE-----
Malthe Borch wrote:
> 2009/3/10 Fred Drake <fdr...@gmail.com>:
>> The change would need to be in zope.tal.
>> I'm ambivalent; while it makes sense to me in isolation, the affect on
>> existing templates is undesirable, and compatibility is a huge deal
>> for this bit of machinery.
> I agree, but it would be interesting to gauge the usage of this
> functionality (e.g. if everyone could put a breakpoint in the right
> place, run their apps and check).
> Actually, I think this is a bug; why would the empty string not be
> printed? If we can agree it's a bug, then I guess it should be fixed
> as part of the general maintenance of the package.
> At any rate, if we did change/fix the behavior, a warning should
> probably be issued. If an attribute == "" then log a warning such as
> "The behavior of this has changed. Make sure your templates are
It seems like we ought to start emitting the warnings first, and then
fold in the new behavior as the default later. Maybe we could allow
some kind of configuration to enable the newer behavior sooner.
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -