bpo-37004: Documented asymmetry of string arguments in difflib.SequenceMatcher for ratio method (GH-13482)
https://bugs.python.org/issue37004
This commit is contained in:
parent
610a4823cc
commit
e9cbcd0018
|
@ -543,6 +543,16 @@ The :class:`SequenceMatcher` class has this constructor:
|
||||||
to try :meth:`quick_ratio` or :meth:`real_quick_ratio` first to get an
|
to try :meth:`quick_ratio` or :meth:`real_quick_ratio` first to get an
|
||||||
upper bound.
|
upper bound.
|
||||||
|
|
||||||
|
.. note::
|
||||||
|
|
||||||
|
Caution: The result of a :meth:`ratio` call may depend on the order of
|
||||||
|
the arguments. For instance::
|
||||||
|
|
||||||
|
>>> SequenceMatcher(None, 'tide', 'diet').ratio()
|
||||||
|
0.25
|
||||||
|
>>> SequenceMatcher(None, 'diet', 'tide').ratio()
|
||||||
|
0.5
|
||||||
|
|
||||||
|
|
||||||
.. method:: quick_ratio()
|
.. method:: quick_ratio()
|
||||||
|
|
||||||
|
|
|
@ -0,0 +1 @@
|
||||||
|
In the documentation for difflib, a note was added explicitly warning that the results of SequenceMatcher's ratio method may depend on the order of the input strings.
|
Loading…
Reference in New Issue