Dieter Maurer wrote:
Tino Wildenhain wrote at 2006-1-13 16:45 +0100:
...
Maybe just have new uZPT with Unicode and leave the "old" ZPT allone?
Maybe with limited ability to "add" old ZPT from ZMI or such.
This would solve the backward-compatibility problems and would be a more
smooth transition w/o the need of upgrade hacks and "strict" hacks
(after all, we arent perl/php ;))
I fear it is not that easy:
Unless we set Python's "defaultencoding" to the site encoding
(and we have such a thing), Python cannot mix Unicode and non-Unicode.
Thus, your "old" ZPT's would need to use only other old ZPT's and
"old" Python scripts and "old" methods (returning encoded texts)
while "strict" ZPT's would need to use only new (strict) ZPT's, scripts
and methods. Quite unfeasible...
Right, and setting Python's default encoding is out of the question.
Regards,
Martijn
_______________________________________________
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 )
