Mirror
/
cpython
mirror of https://github.com/python/cpython
4
1
Fork 0
Code Issues Releases Wiki Activity

Docs: fix typos in documentation (GH-118815)

This commit is contained in:
Xie Yanbo 2024-05-10 16:11:50 +08:00 committed by GitHub
parent 46c808172f
commit 17a2cc199d
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Doc/library/importlib.rst
View File

@ -1252,7 +1252,7 @@ find and load modules.
be only a single binary per framework, and there can be no executable binary be only a single binary per framework, and there can be no executable binary
material outside the Frameworks folder. material outside the Frameworks folder.
To accomodate this requirement, when running on iOS, extension module To accommodate this requirement, when running on iOS, extension module
binaries are *not* packaged as ``.so`` files on ``sys.path``, but as binaries are *not* packaged as ``.so`` files on ``sys.path``, but as
individual standalone frameworks. To discover those frameworks, this loader individual standalone frameworks. To discover those frameworks, this loader
is be registered against the ``.fwork`` file extension, with a ``.fwork`` is be registered against the ``.fwork`` file extension, with a ``.fwork``
@ -1279,7 +1279,7 @@ find and load modules.
When a module is loaded with this loader, the ``__file__`` for the module When a module is loaded with this loader, the ``__file__`` for the module
will report as the location of the ``.fwork`` file. This allows code to use will report as the location of the ``.fwork`` file. This allows code to use
the ``__file__`` of a module as an anchor for file system traveral. the ``__file__`` of a module as an anchor for file system traversal.
However, the spec origin will reference the location of the *actual* binary However, the spec origin will reference the location of the *actual* binary
in the ``.framework`` folder. in the ``.framework`` folder.

2
Doc/library/logging.rst
View File

@ -1204,7 +1204,7 @@ functions.
most programs will want to carefully and explicitly control the logging most programs will want to carefully and explicitly control the logging
configuration, and should therefore prefer creating a module-level logger and configuration, and should therefore prefer creating a module-level logger and
calling :meth:`Logger.debug` (or other level-specific methods) on it, as calling :meth:`Logger.debug` (or other level-specific methods) on it, as
described at the beginnning of this documentation. described at the beginning of this documentation.
.. function:: info(msg, *args, **kwargs) .. function:: info(msg, *args, **kwargs)