Fix a few more references to long integers in the docs.
This commit is contained in:
parent
8055afd019
commit
bf5c6a97f8
|
@ -489,11 +489,11 @@ and the following format units are left untouched.
|
|||
``H`` (integer) [unsigned short int]
|
||||
Convert a C :ctype:`unsigned short int` to a Python integer object.
|
||||
|
||||
``I`` (integer/long) [unsigned int]
|
||||
Convert a C :ctype:`unsigned int` to a Python long integer object.
|
||||
``I`` (integer) [unsigned int]
|
||||
Convert a C :ctype:`unsigned int` to a Python integer object.
|
||||
|
||||
``k`` (integer/long) [unsigned long]
|
||||
Convert a C :ctype:`unsigned long` to a Python long integer object.
|
||||
``k`` (integer) [unsigned long]
|
||||
Convert a C :ctype:`unsigned long` to a Python integer object.
|
||||
|
||||
``L`` (long) [PY_LONG_LONG]
|
||||
Convert a C :ctype:`long long` to a Python integer object. Only available
|
||||
|
|
|
@ -607,7 +607,7 @@ extra checks are performed:
|
|||
|
||||
* Sanity checks of the input arguments are added to frame creation.
|
||||
|
||||
* The storage for long ints is initialized with a known invalid pattern to catch
|
||||
* The storage for ints is initialized with a known invalid pattern to catch
|
||||
reference to uninitialized digits.
|
||||
|
||||
* Low-level tracing and extra exception checking are added to the runtime
|
||||
|
|
|
@ -135,7 +135,7 @@ type objects) *must* have the :attr:`ob_size` field.
|
|||
:attr:`ob_size` field, and the instance size is :attr:`tp_basicsize` plus N
|
||||
times :attr:`tp_itemsize`, where N is the "length" of the object. The value of
|
||||
N is typically stored in the instance's :attr:`ob_size` field. There are
|
||||
exceptions: for example, long ints use a negative :attr:`ob_size` to indicate a
|
||||
exceptions: for example, ints use a negative :attr:`ob_size` to indicate a
|
||||
negative number, and N is ``abs(ob_size)`` there. Also, the presence of an
|
||||
:attr:`ob_size` field in the instance layout doesn't mean that the instance
|
||||
structure is variable-length (for example, the structure for the list type has
|
||||
|
@ -812,7 +812,7 @@ type objects) *must* have the :attr:`ob_size` field.
|
|||
|
||||
where :attr:`tp_basicsize`, :attr:`tp_itemsize` and :attr:`tp_dictoffset` are
|
||||
taken from the type object, and :attr:`ob_size` is taken from the instance. The
|
||||
absolute value is taken because long ints use the sign of :attr:`ob_size` to
|
||||
absolute value is taken because ints use the sign of :attr:`ob_size` to
|
||||
store the sign of the number. (There's never a need to do this calculation
|
||||
yourself; it is done for you by :cfunc:`_PyObject_GetDictPtr`.)
|
||||
|
||||
|
|
|
@ -118,7 +118,7 @@ Number-theoretic and representation functions
|
|||
.. function:: trunc(x)
|
||||
|
||||
Return the :class:`Real` value *x* truncated to an :class:`Integral` (usually
|
||||
a long integer). Delegates to ``x.__trunc__()``.
|
||||
an integer). Delegates to ``x.__trunc__()``.
|
||||
|
||||
|
||||
Note that :func:`frexp` and :func:`modf` have a different call/return pattern
|
||||
|
|
|
@ -65,7 +65,7 @@ which format specific object types.
|
|||
|
||||
.. attribute:: Repr.maxlong
|
||||
|
||||
Maximum number of characters in the representation for a long integer. Digits
|
||||
Maximum number of characters in the representation for an integer. Digits
|
||||
are dropped from the middle. The default is ``40``.
|
||||
|
||||
|
||||
|
|
Loading…
Reference in New Issue