mirror of
https://github.com/python/cpython.git
synced 2025-11-01 10:45:30 +00:00
gh-101100: Fix some broken sphinx references (#107095)
This commit is contained in:
parent
dcd7acb04a
commit
f5147c0cfb
12 changed files with 27 additions and 34 deletions
|
|
@ -1072,8 +1072,8 @@ write the obvious :keyword:`for` loop::
|
|||
|
||||
A related function is :func:`itertools.accumulate(iterable, func=operator.add)
|
||||
<itertools.accumulate>`. It performs the same calculation, but instead of
|
||||
returning only the final result, :func:`accumulate` returns an iterator that
|
||||
also yields each partial result::
|
||||
returning only the final result, :func:`~itertools.accumulate` returns an iterator
|
||||
that also yields each partial result::
|
||||
|
||||
itertools.accumulate([1, 2, 3, 4, 5]) =>
|
||||
1, 3, 6, 10, 15
|
||||
|
|
|
|||
|
|
@ -518,6 +518,8 @@ cache.
|
|||
Compilation Flags
|
||||
-----------------
|
||||
|
||||
.. currentmodule:: re
|
||||
|
||||
Compilation flags let you modify some aspects of how regular expressions work.
|
||||
Flags are available in the :mod:`re` module under two names, a long name such as
|
||||
:const:`IGNORECASE` and a short, one-letter form such as :const:`I`. (If you're
|
||||
|
|
|
|||
|
|
@ -273,7 +273,7 @@ Odds and Ends
|
|||
|
||||
* The sort routines use ``<`` when making comparisons
|
||||
between two objects. So, it is easy to add a standard sort order to a class by
|
||||
defining an :meth:`__lt__` method:
|
||||
defining an :meth:`~object.__lt__` method:
|
||||
|
||||
.. doctest::
|
||||
|
||||
|
|
@ -281,8 +281,8 @@ Odds and Ends
|
|||
>>> sorted(student_objects)
|
||||
[('dave', 'B', 10), ('jane', 'B', 12), ('john', 'A', 15)]
|
||||
|
||||
However, note that ``<`` can fall back to using :meth:`__gt__` if
|
||||
:meth:`__lt__` is not implemented (see :func:`object.__lt__`).
|
||||
However, note that ``<`` can fall back to using :meth:`~object.__gt__` if
|
||||
:meth:`~object.__lt__` is not implemented (see :func:`object.__lt__`).
|
||||
|
||||
* Key functions need not depend directly on the objects being sorted. A key
|
||||
function can also access external resources. For instance, if the student grades
|
||||
|
|
|
|||
|
|
@ -424,8 +424,8 @@ lowercase letters 'ss'.
|
|||
|
||||
A second tool is the :mod:`unicodedata` module's
|
||||
:func:`~unicodedata.normalize` function that converts strings to one
|
||||
of several normal forms, where letters followed by a combining
|
||||
character are replaced with single characters. :func:`normalize` can
|
||||
of several normal forms, where letters followed by a combining character are
|
||||
replaced with single characters. :func:`~unicodedata.normalize` can
|
||||
be used to perform string comparisons that won't falsely report
|
||||
inequality if two strings use combining characters differently:
|
||||
|
||||
|
|
@ -474,8 +474,8 @@ The Unicode Standard also specifies how to do caseless comparisons::
|
|||
|
||||
print(compare_caseless(single_char, multiple_chars))
|
||||
|
||||
This will print ``True``. (Why is :func:`NFD` invoked twice? Because
|
||||
there are a few characters that make :meth:`casefold` return a
|
||||
This will print ``True``. (Why is :func:`!NFD` invoked twice? Because
|
||||
there are a few characters that make :meth:`~str.casefold` return a
|
||||
non-normalized string, so the result needs to be normalized again. See
|
||||
section 3.13 of the Unicode Standard for a discussion and an example.)
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue