PEP 538: cite all 3 common failure modes
This commit is contained in:
parent
61a36c94e2
commit
34d69bad02
|
@ -368,9 +368,10 @@ be slightly different::
|
||||||
PYTHONCOERCECLOCALE=0 to disable this locale coercion behaviour).
|
PYTHONCOERCECLOCALE=0 to disable this locale coercion behaviour).
|
||||||
|
|
||||||
This locale coercion will mean that the standard Python binary should once
|
This locale coercion will mean that the standard Python binary should once
|
||||||
again "just work" in the two main failure cases we're aware of (missing locale
|
again "just work" in the three main failure cases we're aware of (missing locale
|
||||||
settings and SSH forwarding of unknown locales), as long as the target
|
settings, SSH forwarding of unknown locales, and developers explicitly
|
||||||
platform provides at least one of the candidate UTF-8 based environments.
|
requesting ``LANG=C``), as long as the target platform provides at least one
|
||||||
|
of the candidate UTF-8 based environments.
|
||||||
|
|
||||||
If ``PYTHONCOERCECLOCALE=0`` is set, or none of the candidate locales is
|
If ``PYTHONCOERCECLOCALE=0`` is set, or none of the candidate locales is
|
||||||
successfully configured, then initialization will continue as usual in the C
|
successfully configured, then initialization will continue as usual in the C
|
||||||
|
@ -425,6 +426,7 @@ preprocessor definition.
|
||||||
On platforms where they would have no effect (e.g. Mac OS X, iOS, Android,
|
On platforms where they would have no effect (e.g. Mac OS X, iOS, Android,
|
||||||
Windows) these preprocessor variables would always be undefined.
|
Windows) these preprocessor variables would always be undefined.
|
||||||
|
|
||||||
|
|
||||||
Platform Support Changes
|
Platform Support Changes
|
||||||
========================
|
========================
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue