Fix typos and remove deprecated deprecation warning. (GH-17741)

This commit is contained in:
Antoine 2019-12-29 23:14:22 +01:00 committed by Pablo Galindo
parent 8f0703ff92
commit 32a12aed6d

View file

@ -161,13 +161,6 @@ as the ``NULL`` pointer)::
0x1d000000 0x1d000000
>>> >>>
.. note::
:mod:`ctypes` may raise a :exc:`ValueError` after calling the function, if
it detects that an invalid number of arguments were passed. This behavior
should not be relied upon. It is deprecated in 3.6.2, and will be removed
in 3.7.
:exc:`ValueError` is raised when you call an ``stdcall`` function with the :exc:`ValueError` is raised when you call an ``stdcall`` function with the
``cdecl`` calling convention, or vice versa:: ``cdecl`` calling convention, or vice versa::
@ -624,7 +617,7 @@ Structure/union alignment and byte order
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
By default, Structure and Union fields are aligned in the same way the C By default, Structure and Union fields are aligned in the same way the C
compiler does it. It is possible to override this behavior be specifying a compiler does it. It is possible to override this behavior by specifying a
:attr:`_pack_` class attribute in the subclass definition. This must be set to a :attr:`_pack_` class attribute in the subclass definition. This must be set to a
positive integer and specifies the maximum alignment for the fields. This is positive integer and specifies the maximum alignment for the fields. This is
what ``#pragma pack(n)`` also does in MSVC. what ``#pragma pack(n)`` also does in MSVC.
@ -922,7 +915,7 @@ attribute later, after the class statement::
... ("next", POINTER(cell))] ... ("next", POINTER(cell))]
>>> >>>
Lets try it. We create two instances of ``cell``, and let them point to each Let's try it. We create two instances of ``cell``, and let them point to each
other, and finally follow the pointer chain a few times:: other, and finally follow the pointer chain a few times::
>>> c1 = cell() >>> c1 = cell()
@ -1125,8 +1118,8 @@ hit the ``NULL`` entry::
>>> >>>
The fact that standard Python has a frozen module and a frozen package The fact that standard Python has a frozen module and a frozen package
(indicated by the negative size member) is not well known, it is only used for (indicated by the negative ``size`` member) is not well known, it is only used
testing. Try it out with ``import __hello__`` for example. for testing. Try it out with ``import __hello__`` for example.
.. _ctypes-surprises: .. _ctypes-surprises: