mirror of
https://github.com/python/cpython.git
synced 2025-09-26 10:19:53 +00:00
Issue #28763: Use double hyphens (rendered as en-dashes) in numerical ranges
in the documentation.
This commit is contained in:
commit
d80c3fb17b
16 changed files with 24 additions and 24 deletions
|
@ -47,7 +47,7 @@ it's the base calendar for all computations.
|
|||
|
||||
.. method:: itermonthdates(year, month)
|
||||
|
||||
Return an iterator for the month *month* (1-12) in the year *year*. This
|
||||
Return an iterator for the month *month* (1--12) in the year *year*. This
|
||||
iterator will return all days (as :class:`datetime.date` objects) for the
|
||||
month and all days before the start of the month or after the end of the
|
||||
month that are required to get a complete week.
|
||||
|
|
|
@ -309,4 +309,4 @@ cuts for numerical purposes, a good reference should be the following:
|
|||
|
||||
Kahan, W: Branch cuts for complex elementary functions; or, Much ado about
|
||||
nothing's sign bit. In Iserles, A., and Powell, M. (eds.), The state of the art
|
||||
in numerical analysis. Clarendon Press (1987) pp165-211.
|
||||
in numerical analysis. Clarendon Press (1987) pp165--211.
|
||||
|
|
|
@ -858,7 +858,7 @@ Encodings and Unicode
|
|||
---------------------
|
||||
|
||||
Strings are stored internally as sequences of code points in
|
||||
range ``0x0``-``0x10FFFF``. (See :pep:`393` for
|
||||
range ``0x0``--``0x10FFFF``. (See :pep:`393` for
|
||||
more details about the implementation.)
|
||||
Once a string object is used outside of CPU and memory, endianness
|
||||
and how these arrays are stored as bytes become an issue. As with other
|
||||
|
@ -868,7 +868,7 @@ There are a variety of different text serialisation codecs, which are
|
|||
collectivity referred to as :term:`text encodings <text encoding>`.
|
||||
|
||||
The simplest text encoding (called ``'latin-1'`` or ``'iso-8859-1'``) maps
|
||||
the code points 0-255 to the bytes ``0x0``-``0xff``, which means that a string
|
||||
the code points 0--255 to the bytes ``0x0``--``0xff``, which means that a string
|
||||
object that contains code points above ``U+00FF`` can't be encoded with this
|
||||
codec. Doing so will raise a :exc:`UnicodeEncodeError` that looks
|
||||
like the following (although the details of the error message may differ):
|
||||
|
@ -877,7 +877,7 @@ position 3: ordinal not in range(256)``.
|
|||
|
||||
There's another group of encodings (the so called charmap encodings) that choose
|
||||
a different subset of all Unicode code points and how these code points are
|
||||
mapped to the bytes ``0x0``-``0xff``. To see how this is done simply open
|
||||
mapped to the bytes ``0x0``--``0xff``. To see how this is done simply open
|
||||
e.g. :file:`encodings/cp1252.py` (which is an encoding that is used primarily on
|
||||
Windows). There's a string constant with 256 characters that shows you which
|
||||
character is mapped to which byte value.
|
||||
|
|
|
@ -213,7 +213,7 @@ it returns a string.
|
|||
|
||||
Return a string representation of the ASCII character *c*. If *c* is printable,
|
||||
this string is the character itself. If the character is a control character
|
||||
(0x00-0x1f) the string consists of a caret (``'^'``) followed by the
|
||||
(0x00--0x1f) the string consists of a caret (``'^'``) followed by the
|
||||
corresponding uppercase letter. If the character is an ASCII delete (0x7f) the
|
||||
string is ``'^?'``. If the character has its meta bit (0x80) set, the meta bit
|
||||
is stripped, the preceding rules applied, and ``'!'`` prepended to the result.
|
||||
|
|
|
@ -316,7 +316,7 @@ The module :mod:`curses` defines the following functions:
|
|||
Return the name of the key numbered *k*. The name of a key generating printable
|
||||
ASCII character is the key's character. The name of a control-key combination
|
||||
is a two-character string consisting of a caret followed by the corresponding
|
||||
printable ASCII character. The name of an alt-key combination (128-255) is a
|
||||
printable ASCII character. The name of an alt-key combination (128--255) is a
|
||||
string consisting of the prefix 'M-' followed by the name of the corresponding
|
||||
ASCII character.
|
||||
|
||||
|
|
|
@ -692,7 +692,7 @@ are always available. They are listed here in alphabetical order.
|
|||
preceded by ``+`` or ``-`` (with no space in between) and surrounded by
|
||||
whitespace. A base-n literal consists of the digits 0 to n-1, with ``a``
|
||||
to ``z`` (or ``A`` to ``Z``) having
|
||||
values 10 to 35. The default *base* is 10. The allowed values are 0 and 2-36.
|
||||
values 10 to 35. The default *base* is 10. The allowed values are 0 and 2--36.
|
||||
Base-2, -8, and -16 literals can be optionally prefixed with ``0b``/``0B``,
|
||||
``0o``/``0O``, or ``0x``/``0X``, as with integer literals in code. Base 0
|
||||
means to interpret exactly as a code literal, so that the actual base is 2,
|
||||
|
|
|
@ -99,7 +99,7 @@ write code that handles both IP versions correctly.
|
|||
The following constitutes a valid IPv4 address:
|
||||
|
||||
1. A string in decimal-dot notation, consisting of four decimal integers in
|
||||
the inclusive range 0-255, separated by dots (e.g. ``192.168.0.1``). Each
|
||||
the inclusive range 0--255, separated by dots (e.g. ``192.168.0.1``). Each
|
||||
integer represents an octet (byte) in the address. Leading zeroes are
|
||||
tolerated only for values less than 8 (as there is no ambiguity
|
||||
between the decimal and octal interpretations of such strings).
|
||||
|
|
|
@ -345,7 +345,7 @@ Encoders and Decoders
|
|||
|
||||
If *strict* is false (``True`` is the default), then control characters
|
||||
will be allowed inside strings. Control characters in this context are
|
||||
those with character codes in the 0-31 range, including ``'\t'`` (tab),
|
||||
those with character codes in the 0--31 range, including ``'\t'`` (tab),
|
||||
``'\n'``, ``'\r'`` and ``'\0'``.
|
||||
|
||||
If the data being deserialized is not a valid JSON document, a
|
||||
|
|
|
@ -53,7 +53,7 @@ from sources provided by the operating system.
|
|||
|
||||
M. Matsumoto and T. Nishimura, "Mersenne Twister: A 623-dimensionally
|
||||
equidistributed uniform pseudorandom number generator", ACM Transactions on
|
||||
Modeling and Computer Simulation Vol. 8, No. 1, January pp.3-30 1998.
|
||||
Modeling and Computer Simulation Vol. 8, No. 1, January pp.3--30 1998.
|
||||
|
||||
|
||||
`Complementary-Multiply-with-Carry recipe
|
||||
|
|
|
@ -224,9 +224,9 @@ However, for reading convenience, most of the examples show sorted sequences.
|
|||
52.5
|
||||
|
||||
In the following example, the data are rounded, so that each value represents
|
||||
the midpoint of data classes, e.g. 1 is the midpoint of the class 0.5-1.5, 2
|
||||
is the midpoint of 1.5-2.5, 3 is the midpoint of 2.5-3.5, etc. With the data
|
||||
given, the middle value falls somewhere in the class 3.5-4.5, and
|
||||
the midpoint of data classes, e.g. 1 is the midpoint of the class 0.5--1.5, 2
|
||||
is the midpoint of 1.5--2.5, 3 is the midpoint of 2.5--3.5, etc. With the data
|
||||
given, the middle value falls somewhere in the class 3.5--4.5, and
|
||||
interpolation is used to estimate it:
|
||||
|
||||
.. doctest::
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue