Issue 9328: str.format.doc backport glitch (original) (raw)

Created on 2010-07-21 22:49 by terry.reedy, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (5)
msg111130 - (view)	Author: Terry J. Reedy (terry.reedy) *	Date: 2010-07-21 22:49
On Python list, 'jmfauth' reports >>> >>> sys.version 2.7 (r27:82525, Jul 4 2010, 09:01:59) [MSC v.1500 32 bit (Intel)] >>> >>> ''.format.__doc__ S.format(*args, **kwargs) -> unicode I do not have 2.7 loaded to verify this, but assuming this is accurate, 'unicode' should be 'string'. I presume this is from mistaken conversion of 3.1 'string' to 2.7 'unicode' when backporting the new string format system.
msg111138 - (view)	Author: Eric V. Smith (eric.smith) *	Date: 2010-07-22 00:34
Yes, that is what it says; and yes, it should be "string". Although why all of the methods say "string" and not "str" isn't clear to me. Probably historical. The doc string for str.__format__ contains the same error.
msg111139 - (view)	Author: Eric V. Smith (eric.smith) *	Date: 2010-07-22 00:40
And now that I look at it, the subject contains "__format__" but the original message says "format". Both cases are already covered!
msg111142 - (view)	Author: Fred Drake (fdrake)	Date: 2010-07-22 00:46
On Wed, Jul 21, 2010 at 8:34 PM, Eric Smith <report@bugs.python.org> wrote: > Although why all of the methods say "string" and not "str" isn't clear to me. Probably historical. Indeed; we used "string" in the docs as an informal way to say what eventually became known as basestring.   -Fred
msg112181 - (view)	Author: Georg Brandl (georg.brandl) *	Date: 2010-07-31 19:07
Fixed in r83354.