Recent changes to patches

Make HTMLErrorFormatter handle unicode in .myt/.py source

2006-08-29T09:30:15Z

HTMLErrorFormatter isn't cleanly handling unicode characters in .myt and
their compiled .py files. When your .myt raises an exception, and there's
unicode characters nearby the originating line of the exception,
HTMLErrorFormatter will crap out with a UnicodeError when attempting to
print out those source code lines.

Example:

% m.setTYPO_output_encoding('UTF-8')
les pylonautes français
<br />encoding is: <% m.output_encoding %>

Myghty doesn't know what kind of unicode it's going to encounter in
whatever random .myt/.py raises the original exception, so I'm having it
use the 'replace' errors handler during the translations.

Beware: I'm not sure how else the Request.apply_escapes method is used,
so mind my patch to it (maybe give it an errors keyword option instead).

Typos in encoding.py in unicode-opt2

2006-08-29T07:14:30Z

Looks like the tests didn't quite cover this errors property -- there's a
couple typos

List underlying exception type for wrapped exceptions

2005-09-13T17:59:26Z

It would be nice if the error report listed the
underlying type of wrapped exceptions.

Here's a simple patch which does just that.

Reference the URI Cache from the data cache section.

2005-08-31T23:49:32Z

Small documentation patch which adds a reference to the
URI Cache setting from the Data Caching section of the
documentation.