Guillaume Bouchard added the comment:
> str always falls back to the repr; in general str(obj) should always return
> some value, otherwise the assumptions of a *lot* of Python code would be
> broken.
Perhaps it may raises a warning ?
ie, the only reason encoding exists i
New submission from Guillaume Bouchard :
The docstring associated with str() says:
str(string[, encoding[, errors]]) -> str
Create a new string object from the given encoded string.
encoding defaults to the current default string encoding.
errors can be 'strict', 'r
