[2.7] Correct a couple of unbalanced parenthesis. (GH-10779). (GH-10963)
(cherry picked from commit 55f41e45b4
)
This commit is contained in:
parent
358fc87f53
commit
46aa472a8f
|
@ -98,7 +98,7 @@ The new-style Py_buffer struct
|
|||
suboffset value that it negative indicates that no de-referencing should
|
||||
occur (striding in a contiguous memory block).
|
||||
|
||||
If all suboffsets are negative (i.e. no de-referencing is needed, then
|
||||
If all suboffsets are negative (i.e. no de-referencing is needed), then
|
||||
this field must be NULL (the default value).
|
||||
|
||||
Here is a function that returns a pointer to the element in an N-D array
|
||||
|
|
|
@ -286,7 +286,7 @@ However sometimes you have to run the embedded Python interpreter in the same
|
|||
thread as your rest application and you can't allow the
|
||||
:c:func:`PyRun_InteractiveLoop` to stop while waiting for user input. The one
|
||||
solution then is to call :c:func:`PyParser_ParseString` and test for ``e.error``
|
||||
equal to ``E_EOF``, which means the input is incomplete). Here's a sample code
|
||||
equal to ``E_EOF``, which means the input is incomplete. Here's a sample code
|
||||
fragment, untested, inspired by code from Alex Farber::
|
||||
|
||||
#include <Python.h>
|
||||
|
|
|
@ -188,7 +188,7 @@ Other functions
|
|||
|
||||
Windows will return one of:
|
||||
|
||||
- win-amd64 (64bit Windows on AMD64 (aka x86_64, Intel64, EM64T, etc)
|
||||
- win-amd64 (64bit Windows on AMD64, aka x86_64, Intel64, and EM64T)
|
||||
- win-ia64 (64bit Windows on Itanium)
|
||||
- win32 (all others - specifically, sys.platform is returned)
|
||||
|
||||
|
|
Loading…
Reference in New Issue