Commit 5e3a19d8 authored by Senthil Kumaran's avatar Senthil Kumaran

merge from 3.2 - Fix closes Issue12621 - Fix docstrings of find and rfind...

merge from 3.2 - Fix closes Issue12621 - Fix docstrings of find and rfind methods of bytes/bytearry/unicodeobject.
parent 8171cf52
...@@ -1170,7 +1170,7 @@ PyDoc_STRVAR(find__doc__, ...@@ -1170,7 +1170,7 @@ PyDoc_STRVAR(find__doc__,
"B.find(sub [,start [,end]]) -> int\n\ "B.find(sub [,start [,end]]) -> int\n\
\n\ \n\
Return the lowest index in B where subsection sub is found,\n\ Return the lowest index in B where subsection sub is found,\n\
such that sub is contained within s[start,end]. Optional\n\ such that sub is contained within B[start,end]. Optional\n\
arguments start and end are interpreted as in slice notation.\n\ arguments start and end are interpreted as in slice notation.\n\
\n\ \n\
Return -1 on failure."); Return -1 on failure.");
...@@ -1240,7 +1240,7 @@ PyDoc_STRVAR(rfind__doc__, ...@@ -1240,7 +1240,7 @@ PyDoc_STRVAR(rfind__doc__,
"B.rfind(sub [,start [,end]]) -> int\n\ "B.rfind(sub [,start [,end]]) -> int\n\
\n\ \n\
Return the highest index in B where subsection sub is found,\n\ Return the highest index in B where subsection sub is found,\n\
such that sub is contained within s[start,end]. Optional\n\ such that sub is contained within B[start,end]. Optional\n\
arguments start and end are interpreted as in slice notation.\n\ arguments start and end are interpreted as in slice notation.\n\
\n\ \n\
Return -1 on failure."); Return -1 on failure.");
......
...@@ -1727,7 +1727,7 @@ PyDoc_STRVAR(find__doc__, ...@@ -1727,7 +1727,7 @@ PyDoc_STRVAR(find__doc__,
"S.find(sub [,start [,end]]) -> int\n\ "S.find(sub [,start [,end]]) -> int\n\
\n\ \n\
Return the lowest index in S where substring sub is found,\n\ Return the lowest index in S where substring sub is found,\n\
such that sub is contained within s[start:end]. Optional\n\ such that sub is contained within S[start:end]. Optional\n\
arguments start and end are interpreted as in slice notation.\n\ arguments start and end are interpreted as in slice notation.\n\
\n\ \n\
Return -1 on failure."); Return -1 on failure.");
...@@ -1766,7 +1766,7 @@ PyDoc_STRVAR(rfind__doc__, ...@@ -1766,7 +1766,7 @@ PyDoc_STRVAR(rfind__doc__,
"S.rfind(sub [,start [,end]]) -> int\n\ "S.rfind(sub [,start [,end]]) -> int\n\
\n\ \n\
Return the highest index in S where substring sub is found,\n\ Return the highest index in S where substring sub is found,\n\
such that sub is contained within s[start:end]. Optional\n\ such that sub is contained within S[start:end]. Optional\n\
arguments start and end are interpreted as in slice notation.\n\ arguments start and end are interpreted as in slice notation.\n\
\n\ \n\
Return -1 on failure."); Return -1 on failure.");
......
...@@ -6491,7 +6491,7 @@ PyDoc_STRVAR(find__doc__, ...@@ -6491,7 +6491,7 @@ PyDoc_STRVAR(find__doc__,
"S.find(sub [,start [,end]]) -> int\n\ "S.find(sub [,start [,end]]) -> int\n\
\n\ \n\
Return the lowest index in S where substring sub is found,\n\ Return the lowest index in S where substring sub is found,\n\
such that sub is contained within s[start:end]. Optional\n\ such that sub is contained within S[start:end]. Optional\n\
arguments start and end are interpreted as in slice notation.\n\ arguments start and end are interpreted as in slice notation.\n\
\n\ \n\
Return -1 on failure."); Return -1 on failure.");
...@@ -7226,7 +7226,7 @@ PyDoc_STRVAR(rfind__doc__, ...@@ -7226,7 +7226,7 @@ PyDoc_STRVAR(rfind__doc__,
"S.rfind(sub [,start [,end]]) -> int\n\ "S.rfind(sub [,start [,end]]) -> int\n\
\n\ \n\
Return the highest index in S where substring sub is found,\n\ Return the highest index in S where substring sub is found,\n\
such that sub is contained within s[start:end]. Optional\n\ such that sub is contained within S[start:end]. Optional\n\
arguments start and end are interpreted as in slice notation.\n\ arguments start and end are interpreted as in slice notation.\n\
\n\ \n\
Return -1 on failure."); Return -1 on failure.");
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment