mirror of
https://github.com/python/cpython.git
synced 2025-11-01 18:51:43 +00:00
Docs: remove redundant "adverb-adjective" hyphens from compound modifiers (GH-94551)
Discussion: https://discuss.python.org/t/slight-grammar-fix-throughout-adverbs-dont-need-hyphen/17021
This commit is contained in:
parent
2b8ed4d3d4
commit
3440d197a5
71 changed files with 118 additions and 118 deletions
|
|
@ -541,7 +541,7 @@ Let's dive in!
|
|||
|
||||
16. Compile, then run the relevant portions of the regression-test suite.
|
||||
This change should not introduce any new compile-time warnings or errors,
|
||||
and there should be no externally-visible change to Python's behavior.
|
||||
and there should be no externally visible change to Python's behavior.
|
||||
|
||||
Well, except for one difference: ``inspect.signature()`` run on your function
|
||||
should now provide a valid signature!
|
||||
|
|
@ -1117,7 +1117,7 @@ Here's the syntax for cloning a function::
|
|||
``module.class`` in the sample just to illustrate that you must
|
||||
use the full path to *both* functions.)
|
||||
|
||||
Sorry, there's no syntax for partially-cloning a function, or cloning a function
|
||||
Sorry, there's no syntax for partially cloning a function, or cloning a function
|
||||
then modifying it. Cloning is an all-or nothing proposition.
|
||||
|
||||
Also, the function you are cloning from must have been previously defined
|
||||
|
|
@ -1315,7 +1315,7 @@ to specify in your subclass. Here's the current list:
|
|||
there is no default, but not specifying a default may
|
||||
result in an "uninitialized variable" warning. This can
|
||||
easily happen when using option groups—although
|
||||
properly-written code will never actually use this value,
|
||||
properly written code will never actually use this value,
|
||||
the variable does get passed in to the impl, and the
|
||||
C compiler will complain about the "use" of the
|
||||
uninitialized value. This value should always be a
|
||||
|
|
|
|||
|
|
@ -741,7 +741,7 @@ further because you risk skipping a discarded element.
|
|||
The itertools module
|
||||
====================
|
||||
|
||||
The :mod:`itertools` module contains a number of commonly-used iterators as well
|
||||
The :mod:`itertools` module contains a number of commonly used iterators as well
|
||||
as functions for combining several iterators. This section will introduce the
|
||||
module's contents by showing small examples.
|
||||
|
||||
|
|
|
|||
|
|
@ -123,7 +123,7 @@ Sufficiently modern readelf can print the metadata::
|
|||
Arguments: 8@%rbp 8@%r12 -4@%eax
|
||||
|
||||
The above metadata contains information for SystemTap describing how it
|
||||
can patch strategically-placed machine code instructions to enable the
|
||||
can patch strategically placed machine code instructions to enable the
|
||||
tracing hooks used by a SystemTap script.
|
||||
|
||||
|
||||
|
|
@ -410,7 +410,7 @@ needing to directly name the static markers:
|
|||
|
||||
|
||||
The following script uses the tapset above to provide a top-like view of all
|
||||
running CPython code, showing the top 20 most frequently-entered bytecode
|
||||
running CPython code, showing the top 20 most frequently entered bytecode
|
||||
frames, each second, across the whole system:
|
||||
|
||||
.. code-block:: none
|
||||
|
|
|
|||
|
|
@ -127,7 +127,7 @@ Logging to a file
|
|||
^^^^^^^^^^^^^^^^^
|
||||
|
||||
A very common situation is that of recording logging events in a file, so let's
|
||||
look at that next. Be sure to try the following in a newly-started Python
|
||||
look at that next. Be sure to try the following in a newly started Python
|
||||
interpreter, and don't just continue from the session described above::
|
||||
|
||||
import logging
|
||||
|
|
|
|||
|
|
@ -949,7 +949,7 @@ Additionally, you can retrieve named groups as a dictionary with
|
|||
>>> m.groupdict()
|
||||
{'first': 'Jane', 'last': 'Doe'}
|
||||
|
||||
Named groups are handy because they let you use easily-remembered names, instead
|
||||
Named groups are handy because they let you use easily remembered names, instead
|
||||
of having to remember numbers. Here's an example RE from the :mod:`imaplib`
|
||||
module::
|
||||
|
||||
|
|
|
|||
|
|
@ -420,7 +420,7 @@ Openers and Handlers
|
|||
====================
|
||||
|
||||
When you fetch a URL you use an opener (an instance of the perhaps
|
||||
confusingly-named :class:`urllib.request.OpenerDirector`). Normally we have been using
|
||||
confusingly named :class:`urllib.request.OpenerDirector`). Normally we have been using
|
||||
the default opener - via ``urlopen`` - but you can create custom
|
||||
openers. Openers use handlers. All the "heavy lifting" is done by the
|
||||
handlers. Each handler knows how to open URLs for a particular URL scheme (http,
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue