Fixed typos (#1144)
This commit is contained in:
parent
5326c3a38d
commit
19b5d9586a
|
@ -289,7 +289,7 @@ Fail-over mechanism
|
||||||
Clients that are browsing PyPI should be able to use a fail-over
|
Clients that are browsing PyPI should be able to use a fail-over
|
||||||
mechanism when PyPI or the used mirror is not responding.
|
mechanism when PyPI or the used mirror is not responding.
|
||||||
|
|
||||||
It is up to the client to decide wich mirror should be used, maybe by
|
It is up to the client to decide which mirror should be used, maybe by
|
||||||
looking at its geographical location and its responsiveness.
|
looking at its geographical location and its responsiveness.
|
||||||
|
|
||||||
This PEP does not describe how this fail-over mechanism should work,
|
This PEP does not describe how this fail-over mechanism should work,
|
||||||
|
@ -316,7 +316,7 @@ compatible with any package index server out there.
|
||||||
|
|
||||||
Software that are compatible with PyPI and Distutils so far:
|
Software that are compatible with PyPI and Distutils so far:
|
||||||
|
|
||||||
- PloneSoftwareCenter [#psc]_ wich is used to run plone.org products section.
|
- PloneSoftwareCenter [#psc]_ which is used to run plone.org products section.
|
||||||
- EggBasket [#eggbasket]_.
|
- EggBasket [#eggbasket]_.
|
||||||
|
|
||||||
**An extra package index is not a mirror of PyPI, but can have some
|
**An extra package index is not a mirror of PyPI, but can have some
|
||||||
|
|
|
@ -412,7 +412,7 @@ The value of the macro ``Py_HASH_ALGORITHM`` defines which hash algorithm is
|
||||||
used internally. It may be set to any of the three values ``Py_HASH_SIPHASH24``,
|
used internally. It may be set to any of the three values ``Py_HASH_SIPHASH24``,
|
||||||
``Py_HASH_FNV`` or ``Py_HASH_EXTERNAL``. If ``Py_HASH_ALGORITHM`` is not
|
``Py_HASH_FNV`` or ``Py_HASH_EXTERNAL``. If ``Py_HASH_ALGORITHM`` is not
|
||||||
defined at all, then the best available algorithm is selected. On platforms
|
defined at all, then the best available algorithm is selected. On platforms
|
||||||
wich don't require aligned memory access (``HAVE_ALIGNED_REQUIRED`` not
|
which don't require aligned memory access (``HAVE_ALIGNED_REQUIRED`` not
|
||||||
defined) and an unsigned 64 bit integer type ``PY_UINT64_T``, SipHash24 is
|
defined) and an unsigned 64 bit integer type ``PY_UINT64_T``, SipHash24 is
|
||||||
used. On strict C89 platforms without a 64 bit data type, or architectures such
|
used. On strict C89 platforms without a 64 bit data type, or architectures such
|
||||||
as SPARC, FNV is selected as fallback. A hash algorithm can be selected with
|
as SPARC, FNV is selected as fallback. A hash algorithm can be selected with
|
||||||
|
|
|
@ -70,7 +70,7 @@ While :pep:`543` defines an API, the PEP would only make sense if it
|
||||||
comes with at least one complete and good implementation. The first
|
comes with at least one complete and good implementation. The first
|
||||||
implementation would ideally be based on the ``ssl`` module of the Python
|
implementation would ideally be based on the ``ssl`` module of the Python
|
||||||
standard library, as this is shipped to all users by default and can be used as
|
standard library, as this is shipped to all users by default and can be used as
|
||||||
a fallback implementation in the absence of anything more targetted.
|
a fallback implementation in the absence of anything more targeted.
|
||||||
|
|
||||||
If this backport is not performed, the only baseline implementation that could
|
If this backport is not performed, the only baseline implementation that could
|
||||||
be used would be pyOpenSSL. This is problematic, however, because of the
|
be used would be pyOpenSSL. This is problematic, however, because of the
|
||||||
|
|
|
@ -744,7 +744,7 @@ Path Configuration
|
||||||
|
|
||||||
If at least one "output field" is not set, Python computes the path
|
If at least one "output field" is not set, Python computes the path
|
||||||
configuration to fill unset fields. If ``module_search_paths_set`` is
|
configuration to fill unset fields. If ``module_search_paths_set`` is
|
||||||
equal to 0, ``module_search_paths`` is overriden and
|
equal to 0, ``module_search_paths`` is overridden and
|
||||||
``module_search_paths_set`` is set to 1.
|
``module_search_paths_set`` is set to 1.
|
||||||
|
|
||||||
It is possible to completely ignore the function computing the default
|
It is possible to completely ignore the function computing the default
|
||||||
|
|
|
@ -559,7 +559,7 @@ nested function must be recomputed each time the nested function is
|
||||||
defined. For certain "functional" styles of programming this may make
|
defined. For certain "functional" styles of programming this may make
|
||||||
switch unattractive in nested functions. (Unless all case expressions
|
switch unattractive in nested functions. (Unless all case expressions
|
||||||
are compile-time constants; then the compiler is of course free to
|
are compile-time constants; then the compiler is of course free to
|
||||||
optimize away the swich freezing code and make the dispatch table part
|
optimize away the switch freezing code and make the dispatch table part
|
||||||
of the code object.)
|
of the code object.)
|
||||||
|
|
||||||
Another downside is that under this option, there's no clear moment
|
Another downside is that under this option, there's no clear moment
|
||||||
|
|
Loading…
Reference in New Issue