Logged In: YES 
user_id=3066

This request is making me reconsider some other changes that
have already been made on the trunk (and are now in 2.5b1).

Reading this, I thought "Doesn't it already do that?"  Turns
out that in Python 2.4, it doesn't.  Both versions handle
this in parsed character data; the difference is confined to
attribute values.

I'd like to propose adding a Boolean configuration attribute
on the parser instance that, when set, causes the parser to
decode entity and character references.  By default, it
would be unset.  This would support backward compatibility
and make it easier to get attribute value decoding.

Another possibility would be to revert the new feature and
add a separate method to perform the decoding.