Issue #27125: Fix various errors like “will [be] inherited”
This commit is contained in:
parent
e8a175eaa0
commit
8d56c026a5
|
@ -56,7 +56,7 @@ The class can be used to simulate nested scopes and is useful in templating.
|
|||
dictionary is provided so that a new chain always has at least one mapping.
|
||||
|
||||
The underlying mappings are stored in a list. That list is public and can
|
||||
accessed or updated using the *maps* attribute. There is no other state.
|
||||
be accessed or updated using the *maps* attribute. There is no other state.
|
||||
|
||||
Lookups search the underlying mappings successively until a key is found. In
|
||||
contrast, writes, updates, and deletions only operate on the first mapping.
|
||||
|
|
|
@ -2478,7 +2478,7 @@ the connection.)
|
|||
|
||||
If authentication is requested but no authentication key is specified then the
|
||||
return value of ``current_process().authkey`` is used (see
|
||||
:class:`~multiprocessing.Process`). This value will automatically inherited by
|
||||
:class:`~multiprocessing.Process`). This value will be automatically inherited by
|
||||
any :class:`~multiprocessing.Process` object that the current process creates.
|
||||
This means that (by default) all processes of a multi-process program will share
|
||||
a single authentication key which can be used when setting up connections
|
||||
|
|
|
@ -3486,7 +3486,7 @@ operating system.
|
|||
|
||||
.. data:: SCHED_RESET_ON_FORK
|
||||
|
||||
This flag can OR'ed with any other scheduling policy. When a process with
|
||||
This flag can be OR'ed with any other scheduling policy. When a process with
|
||||
this flag set forks, its child's scheduling policy and priority are reset to
|
||||
the default.
|
||||
|
||||
|
|
|
@ -244,7 +244,8 @@ variables which either control lexical analysis or can be used for debugging:
|
|||
This attribute is ``None`` by default. If you assign a string to it, that
|
||||
string will be recognized as a lexical-level inclusion request similar to the
|
||||
``source`` keyword in various shells. That is, the immediately following token
|
||||
will opened as a filename and input taken from that stream until EOF, at which
|
||||
will be opened as a filename and input will
|
||||
be taken from that stream until EOF, at which
|
||||
point the :meth:`~io.IOBase.close` method of that stream will be called and
|
||||
the input source will again become the original input stream. Source
|
||||
requests may be stacked any number of levels deep.
|
||||
|
|
|
@ -156,7 +156,7 @@ You can use multiple inheritance with :class:`Generic`::
|
|||
class LinkedList(Sized, Generic[T]):
|
||||
...
|
||||
|
||||
When inheriting from generic classes, some type variables could fixed::
|
||||
When inheriting from generic classes, some type variables could be fixed::
|
||||
|
||||
from typing import TypeVar, Mapping
|
||||
|
||||
|
|
|
@ -3154,7 +3154,7 @@ Port-Specific Changes: Mac OS X
|
|||
:func:`macostools.touched` function to be removed because it depended on the
|
||||
:mod:`macfs` module. (:issue:`1490190`)
|
||||
|
||||
* Many other Mac OS modules have been deprecated and will removed in
|
||||
* Many other Mac OS modules have been deprecated and will be removed in
|
||||
Python 3.0:
|
||||
:mod:`_builtinSuites`,
|
||||
:mod:`aepack`,
|
||||
|
|
|
@ -850,7 +850,8 @@ class ChainMap(MutableMapping):
|
|||
to create a single, updateable view.
|
||||
|
||||
The underlying mappings are stored in a list. That list is public and can
|
||||
accessed or updated using the *maps* attribute. There is no other state.
|
||||
be accessed or updated using the *maps* attribute. There is no other
|
||||
state.
|
||||
|
||||
Lookups search the underlying mappings successively until a key is found.
|
||||
In contrast, writes, updates, and deletions only operate on the first
|
||||
|
|
|
@ -710,7 +710,7 @@ class Message:
|
|||
message, it will be set to "text/plain" and the new parameter and
|
||||
value will be appended as per RFC 2045.
|
||||
|
||||
An alternate header can specified in the header argument, and all
|
||||
An alternate header can be specified in the header argument, and all
|
||||
parameters will be quoted as necessary unless requote is False.
|
||||
|
||||
If charset is specified, the parameter will be encoded according to RFC
|
||||
|
|
|
@ -255,8 +255,8 @@ class HeaderTests(TestCase):
|
|||
self.assertIn(b'\xa0NonbreakSpace: value', conn._buffer)
|
||||
|
||||
def test_ipv6host_header(self):
|
||||
# Default host header on IPv6 transaction should wrapped by [] if
|
||||
# its actual IPv6 address
|
||||
# Default host header on IPv6 transaction should be wrapped by [] if
|
||||
# it is an IPv6 address
|
||||
expected = b'GET /foo HTTP/1.1\r\nHost: [2001::]:81\r\n' \
|
||||
b'Accept-Encoding: identity\r\n\r\n'
|
||||
conn = client.HTTPConnection('[2001::]:81')
|
||||
|
|
|
@ -1052,7 +1052,7 @@ class InputOnly(TixWidget):
|
|||
|
||||
class LabelEntry(TixWidget):
|
||||
"""LabelEntry - Entry field with label. Packages an entry widget
|
||||
and a label into one mega widget. It can beused be used to simplify
|
||||
and a label into one mega widget. It can be used be used to simplify
|
||||
the creation of ``entry-form'' type of interface.
|
||||
|
||||
Subwidgets Class
|
||||
|
|
|
@ -6633,7 +6633,7 @@ C-API
|
|||
PyErr_Format, on machines with HAVE_LONG_LONG defined.
|
||||
|
||||
- Issue #6151: Made PyDescr_COMMON conform to standard C (like PyObject_HEAD in
|
||||
PEP 3123). The PyDescr_TYPE and PyDescr_NAME macros should be should used for
|
||||
PEP 3123). The PyDescr_TYPE and PyDescr_NAME macros should be used for
|
||||
accessing the d_type and d_name members of structures using PyDescr_COMMON.
|
||||
|
||||
- Issue #6405: Remove duplicate type declarations in descrobject.h.
|
||||
|
@ -16065,7 +16065,7 @@ Core and builtins
|
|||
- All standard iterators now ensure that, once StopIteration has been
|
||||
raised, all future calls to next() on the same iterator will also
|
||||
raise StopIteration. There used to be various counterexamples to
|
||||
this behavior, which could caused confusion or subtle program
|
||||
this behavior, which could have caused confusion or subtle program
|
||||
breakage, without any benefits. (Note that this is still an
|
||||
iterator's responsibility; the iterator framework does not enforce
|
||||
this.)
|
||||
|
|
|
@ -1865,7 +1865,7 @@ _PyObject_DebugTypeStats(FILE *out)
|
|||
|
||||
/* These methods are used to control infinite recursion in repr, str, print,
|
||||
etc. Container objects that may recursively contain themselves,
|
||||
e.g. builtin dictionaries and lists, should used Py_ReprEnter() and
|
||||
e.g. builtin dictionaries and lists, should use Py_ReprEnter() and
|
||||
Py_ReprLeave() to avoid infinite recursion.
|
||||
|
||||
Py_ReprEnter() returns 0 the first time it is called for a particular
|
||||
|
|
2
README
2
README
|
@ -58,7 +58,7 @@ PGO takes advantage of recent versions of the GCC or Clang compilers.
|
|||
If ran, the "profile-opt" rule will do several steps.
|
||||
|
||||
First, the entire Python directory is cleaned of temporary files that
|
||||
may resulted in a previous compilation.
|
||||
may have resulted in a previous compilation.
|
||||
|
||||
Then, an instrumented version of the interpreter is built, using suitable
|
||||
compiler flags for each flavour. Note that this is just an intermediary
|
||||
|
|
Loading…
Reference in New Issue