Minor textual edits of PEP 587. (#1055)
This commit is contained in:
parent
b5a4f071d5
commit
4e0a7443f4
12
pep-0587.rst
12
pep-0587.rst
|
@ -21,8 +21,8 @@ computes the module search paths (``sys.path``).
|
|||
|
||||
Building a customized Python which behaves as regular Python becomes
|
||||
easier using the new ``Py_RunMain()`` function. Moreover, command line
|
||||
arguments passed to ``PyConfig.argv`` are now parsed as the regular
|
||||
Python parses command line options, and ``PyConfig.xoptions`` are
|
||||
arguments passed to ``PyConfig.argv`` are now parsed the same way the
|
||||
regular Python parses command line options, and ``PyConfig.xoptions`` are
|
||||
handled as ``-X opt`` command line options.
|
||||
|
||||
This extracts a subset of the API design from the PEP 432 development and
|
||||
|
@ -303,7 +303,7 @@ disabled by default in ``PyPreConfig``. Set ``coerce_c_locale``,
|
|||
enable them depending on the user configuration. In this case, it's
|
||||
safer to explicitly pre-initialize Python to ensure that encodings are
|
||||
configured before the Python initialization starts. Example to get the
|
||||
same encoding than regular Python::
|
||||
same encoding as regular Python::
|
||||
|
||||
PyPreConfig preconfig = PyPreConfig_INIT;
|
||||
preconfig.coerce_c_locale = -1;
|
||||
|
@ -378,8 +378,8 @@ failure or exit using ``Py_INIT_FAILED()`` and ``Py_ExitInitError()``.
|
|||
* ``base_prefix`` (``wchar_t*``, default: ``NULL``):
|
||||
``sys.base_prefix``.
|
||||
* ``buffered_stdio`` (``int``, default: 1):
|
||||
If equals to 0, enable unbuffered mode, make stdout and stderr streams
|
||||
to be unbuffered.
|
||||
If equals to 0, enable unbuffered mode, making the stdout and stderr streams
|
||||
unbuffered.
|
||||
* ``bytes_warning`` (``int``, default: 0):
|
||||
If equals to 1, issue a warning when comparing ``bytes`` or
|
||||
``bytearray`` with ``str``, or comparing ``bytes`` with ``int``. If
|
||||
|
@ -695,7 +695,7 @@ be used before Python pre-initialization, whereas calling directly
|
|||
``malloc()`` and ``free()`` is always safe.
|
||||
|
||||
For ``PyPreConfig`` and constant ``PyConfig``, the caller is responsible
|
||||
to manage dynamically allocated memory; constant strings and constant
|
||||
for managing dynamically allocated memory; constant strings and constant
|
||||
string lists can be used to avoid memory allocations.
|
||||
|
||||
Dynamic ``PyConfig`` requires to call ``PyConfig_Clear()`` to release
|
||||
|
|
Loading…
Reference in New Issue