[issue16072] fix documentation of string.replace() signature

2012-09-28 Thread Andrew Svetlov
Andrew Svetlov added the comment: Fixed in c34a177d1f38 -- resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed ___ Python tracker ___ __

[issue16072] fix documentation of string.replace() signature

2012-09-28 Thread Andrew Svetlov
Andrew Svetlov added the comment: If you want just to change parameter name in the docs — I'm ok with that. -- ___ Python tracker ___

[issue16072] fix documentation of string.replace() signature

2012-09-28 Thread Chris Jerdonek
Chris Jerdonek added the comment: [Reopening] It looks like at least *some* change is warranted here. Notice that all the functions document "s" for the string argument but string.replace() documents "str". However, we have (in 2.7): >>> string.replace(str='aab', old='a', new='b') Traceback

[issue16072] fix documentation of string.replace() signature

2012-09-28 Thread Andrew Svetlov
Andrew Svetlov added the comment: No it shoudn't. It works exactly as described: Return a copy of string *str* with all occurrences of substring *old* replaced by *new*. If the optional argument *maxreplace* is given, the first *maxreplace* occurrences are replaced. *str* is updated string and

[issue16072] fix documentation of string.replace() signature

2012-09-28 Thread Chris Jerdonek
Chris Jerdonek added the comment: Thanks, Andrew. I didn't look closely enough when reading the e-mail or I wouldn't have posted. I had assumed from the e-mail that this was in the string *method* section rather than string module. -- ___ Python t

[issue16072] fix documentation of string.replace() signature

2012-09-27 Thread Chris Jerdonek
New submission from Chris Jerdonek: > Date: Thu, 13 Sep 2012 09:42:47 -0400 > To: > Subject: [docs] Problem with the documentation for string.replace > > >From http://docs.python.org/library/string.html > > string.replace(str, old, new[, > maxreplace])?