bpo-33892: Doc: Use gender neutral words (GH-7770)
(cherry picked from commit 5092439c2c
)
Co-authored-by: Andrés Delfino <adelfino@gmail.com>
This commit is contained in:
parent
6bb7704451
commit
5f165851b9
|
@ -35,7 +35,7 @@ operate within the bounds of the private heap.
|
|||
|
||||
It is important to understand that the management of the Python heap is
|
||||
performed by the interpreter itself and that the user has no control over it,
|
||||
even if she regularly manipulates object pointers to memory blocks inside that
|
||||
even if they regularly manipulate object pointers to memory blocks inside that
|
||||
heap. The allocation of heap space for Python objects and other internal
|
||||
buffers is performed on demand by the Python memory manager through the Python/C
|
||||
API functions listed in this document.
|
||||
|
|
|
@ -21,7 +21,7 @@ specialty---writing code and creating source distributions---while an
|
|||
intermediary species called *packagers* springs up to turn source distributions
|
||||
into built distributions for as many platforms as there are packagers.
|
||||
|
||||
Of course, the module developer could be his own packager; or the packager could
|
||||
Of course, the module developer could be their own packager; or the packager could
|
||||
be a volunteer "out there" somewhere who has access to a platform which the
|
||||
original developer does not; or it could be software periodically grabbing new
|
||||
source distributions and turning them into built distributions for as many
|
||||
|
|
|
@ -94,7 +94,7 @@ containing your setup script :file:`setup.py`, and your module :file:`foo.py`.
|
|||
The archive file will be named :file:`foo-1.0.tar.gz` (or :file:`.zip`), and
|
||||
will unpack into a directory :file:`foo-1.0`.
|
||||
|
||||
If an end-user wishes to install your :mod:`foo` module, all she has to do is
|
||||
If an end-user wishes to install your :mod:`foo` module, all they have to do is
|
||||
download :file:`foo-1.0.tar.gz` (or :file:`.zip`), unpack it, and---from the
|
||||
:file:`foo-1.0` directory---run ::
|
||||
|
||||
|
|
|
@ -546,7 +546,7 @@ on the hash function used in digital signatures.
|
|||
preparer, generates all or part of a message to be signed by a second
|
||||
party, the message signer. If the message preparer is able to find
|
||||
cryptographic hash function collisions (i.e., two messages producing the
|
||||
same hash value), then she might prepare meaningful versions of the message
|
||||
same hash value), then they might prepare meaningful versions of the message
|
||||
that would produce the same hash value and digital signature, but with
|
||||
different results (e.g., transferring $1,000,000 to an account, rather than
|
||||
$10). Cryptographic hash functions have been designed with collision
|
||||
|
|
|
@ -1677,7 +1677,7 @@ The callback function should raise :exc:`OptionValueError` if there are any
|
|||
problems with the option or its argument(s). :mod:`optparse` catches this and
|
||||
terminates the program, printing the error message you supply to stderr. Your
|
||||
message should be clear, concise, accurate, and mention the option at fault.
|
||||
Otherwise, the user will have a hard time figuring out what he did wrong.
|
||||
Otherwise, the user will have a hard time figuring out what they did wrong.
|
||||
|
||||
|
||||
.. _optparse-callback-example-1:
|
||||
|
|
|
@ -1447,8 +1447,8 @@ Finding all Adverbs
|
|||
^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
:func:`findall` matches *all* occurrences of a pattern, not just the first
|
||||
one as :func:`search` does. For example, if one was a writer and wanted to
|
||||
find all of the adverbs in some text, he or she might use :func:`findall` in
|
||||
one as :func:`search` does. For example, if a writer wanted to
|
||||
find all of the adverbs in some text, they might use :func:`findall` in
|
||||
the following manner::
|
||||
|
||||
>>> text = "He was carefully disguised but captured quickly by police."
|
||||
|
@ -1462,8 +1462,8 @@ Finding all Adverbs and their Positions
|
|||
If one wants more information about all matches of a pattern than the matched
|
||||
text, :func:`finditer` is useful as it provides :ref:`match objects
|
||||
<match-objects>` instead of strings. Continuing with the previous example, if
|
||||
one was a writer who wanted to find all of the adverbs *and their positions* in
|
||||
some text, he or she would use :func:`finditer` in the following manner::
|
||||
a writer wanted to find all of the adverbs *and their positions* in
|
||||
some text, they would use :func:`finditer` in the following manner::
|
||||
|
||||
>>> text = "He was carefully disguised but captured quickly by police."
|
||||
>>> for m in re.finditer(r"\w+ly", text):
|
||||
|
|
|
@ -1991,7 +1991,7 @@ message with one of the parts, you can decrypt it with the other part, and
|
|||
|
||||
A certificate contains information about two principals. It contains the name
|
||||
of a *subject*, and the subject's public key. It also contains a statement by a
|
||||
second principal, the *issuer*, that the subject is who he claims to be, and
|
||||
second principal, the *issuer*, that the subject is who they claim to be, and
|
||||
that this is indeed the subject's public key. The issuer's statement is signed
|
||||
with the issuer's private key, which only the issuer knows. However, anyone can
|
||||
verify the issuer's statement by finding the issuer's public key, decrypting the
|
||||
|
|
|
@ -143,12 +143,12 @@ to escape quotes::
|
|||
"doesn't"
|
||||
>>> "doesn't" # ...or use double quotes instead
|
||||
"doesn't"
|
||||
>>> '"Yes," he said.'
|
||||
'"Yes," he said.'
|
||||
>>> "\"Yes,\" he said."
|
||||
'"Yes," he said.'
|
||||
>>> '"Isn\'t," she said.'
|
||||
'"Isn\'t," she said.'
|
||||
>>> '"Yes," they said.'
|
||||
'"Yes," they said.'
|
||||
>>> "\"Yes,\" they said."
|
||||
'"Yes," they said.'
|
||||
>>> '"Isn\'t," they said.'
|
||||
'"Isn\'t," they said.'
|
||||
|
||||
In the interactive interpreter, the output string is enclosed in quotes and
|
||||
special characters are escaped with backslashes. While this might sometimes
|
||||
|
@ -159,10 +159,10 @@ enclosed in single quotes. The :func:`print` function produces a more
|
|||
readable output, by omitting the enclosing quotes and by printing escaped
|
||||
and special characters::
|
||||
|
||||
>>> '"Isn\'t," she said.'
|
||||
'"Isn\'t," she said.'
|
||||
>>> print('"Isn\'t," she said.')
|
||||
"Isn't," she said.
|
||||
>>> '"Isn\'t," they said.'
|
||||
'"Isn\'t," they said.'
|
||||
>>> print('"Isn\'t," they said.')
|
||||
"Isn't," they said.
|
||||
>>> s = 'First line.\nSecond line.' # \n means newline
|
||||
>>> s # without print(), \n is included in the output
|
||||
'First line.\nSecond line.'
|
||||
|
|
Loading…
Reference in New Issue