On Sep 17, 2007, at 5:17 PM, Michael Watkins wrote:

> However slippery fingers caused the draft email to be sent anyway -
> please disregard.
>
> (although I suppose someone somewhere might want to subclass u8/h8 -
> heads up still in order)

Actually, this happens to have been on my mind in the last coupld of
days,
as I have been thinking about what qpy should become in python 3, where
the unification of str and unicode, and the wider use of utf8
encoding seems
to make the u8/h8 division obsolete.

I'm thinking of a new class named "html" to replace h8, and using
python3's str
class directly instead of defining any separate u8-type class.
I'm also thinking of changing the templates to allow [str] instead of
[plain] as the
distinguishing mark.

I think this can be implemented with less code, and we can add some
synonyms so that common qpy code will run without modification.

Should the new html class be written (in C) specifically to be
subclass-able?
The cost is that html-combining operations, which may be executed
at a very high frequency in common applications, will be slower.
I'm not sure.