[issue35318] Check accuracy of str() doc string for its encoding argument

Martin Panter added the comment: Closing in favour of Issue 39574 where a new wording is proposed -- nosy: +martin.panter resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> str.__doc__ is misleading ___ Python

[issue35318] Check accuracy of str() doc string for its encoding argument

Serhiy Storchaka added the comment: Is not it exactly what the docsting says? > If encoding or > errors is specified, then the object must expose a data buffer > that will be decoded using the given encoding and error handler. > Otherwise, returns the result of object.__str__() (if defined) >

[issue35318] Check accuracy of str() doc string for its encoding argument

Raymond Hettinger added the comment: We may need to reword this a bit to show that the default system encoding only applies if "errors" is specified; otherwise, the argument pattern is mysterious. -- ___ Python tracker

[issue35318] Check accuracy of str() doc string for its encoding argument

Serhiy Storchaka added the comment: >>> str(buffer, errors='strict') 'lim x ⟶ ∞, 1/sin²(x)' -- nosy: +serhiy.storchaka ___ Python tracker ___

[issue35318] Check accuracy of str() doc string for its encoding argument

New submission from Raymond Hettinger : The "encoding" parameter is documented to default to sys.getdefaultencoding(). That may be true but there doesn't seem to be a way to use that default because objects will all have a __str__ or __repr__ that will be run instead.