mirrors/cpython
1
0
Fork 0
mirror of https://github.com/python/cpython.git synced 2025-11-13 07:26:31 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 9

Markup consistency.

Browse source
This commit is contained in:
Fred Drake 1998-04-03 06:21:23 +00:00
parent 5bfe4850cf
commit 9fee071ab6
2 changed files with 22 additions and 20 deletions
Download patch file Download diff file Expand all files Collapse all files

21
Doc/lib/liblocale.tex
View file

@ -203,7 +203,7 @@ implementation are broken in such a way that frequent locale changes
may cause core dumps. This makes the locale somewhat painful to use may cause core dumps. This makes the locale somewhat painful to use
correctly. correctly.
Initially, when a program is started, the locale is the "C" locale, no Initially, when a program is started, the locale is the \samp{C} locale, no
matter what the user's preferred locale is. The program must matter what the user's preferred locale is. The program must
explicitly say that it wants the user's preferred locale settings by explicitly say that it wants the user's preferred locale settings by
calling \code{setlocale(LC_ALL, "")}. calling \code{setlocale(LC_ALL, "")}.
@ -219,8 +219,8 @@ independent version of an operation that is affected by the locale
\function{time.strftime()})), you will have to find a way to do it \function{time.strftime()})), you will have to find a way to do it
without using the standard library routine. Even better is convincing without using the standard library routine. Even better is convincing
yourself that using locale settings is okay. Only as a last resort yourself that using locale settings is okay. Only as a last resort
should you document that your module is not compatible with non-C should you document that your module is not compatible with
locale settings. non-\samp{C} locale settings.
The case conversion functions in the The case conversion functions in the
\module{string}\refstmodindex{string} and \module{string}\refstmodindex{string} and
@ -240,30 +240,31 @@ is to use the special functions defined by this module:
\function{str()}. \function{str()}.
\subsection{For extension writers and programs that embed Python} \subsection{For extension writers and programs that embed Python}
\label{embedding-locale}
Extension modules should never call \function{setlocale()}, except to Extension modules should never call \function{setlocale()}, except to
find out what the current locale is. But since the return value can find out what the current locale is. But since the return value can
only be used portably to restore it, that is not very useful (except only be used portably to restore it, that is not very useful (except
perhaps to find out whether or not the locale is ``C''). perhaps to find out whether or not the locale is \samp{C}).
When Python is embedded in an application, if the application sets the When Python is embedded in an application, if the application sets the
locale to something specific before initializing Python, that is locale to something specific before initializing Python, that is
generally okay, and Python will use whatever locale is set, generally okay, and Python will use whatever locale is set,
\strong{except} that the \constant{LC_NUMERIC} locale should always be \emph{except} that the \constant{LC_NUMERIC} locale should always be
``C''. \samp{C}.
The \function{setlocale()} function in the \module{locale} module contains The \function{setlocale()} function in the \module{locale} module contains
gives the Python progammer the impression that you can manipulate the gives the Python progammer the impression that you can manipulate the
\constant{LC_NUMERIC} locale setting, but this not the case at the C \constant{LC_NUMERIC} locale setting, but this not the case at the \C{}
level: C code will always find that the \constant{LC_NUMERIC} locale level: \C{} code will always find that the \constant{LC_NUMERIC} locale
setting is ``C''. This is because too much would break when the setting is \samp{C}. This is because too much would break when the
decimal point character is set to something else than a period decimal point character is set to something else than a period
(e.g. the Python parser would break). Caveat: threads that run (e.g. the Python parser would break). Caveat: threads that run
without holding Python's global interpreter lock may occasionally find without holding Python's global interpreter lock may occasionally find
that the numeric locale setting differs; this is because the only that the numeric locale setting differs; this is because the only
portable way to implement this feature is to set the numeric locale portable way to implement this feature is to set the numeric locale
settings to what the user requests, extract the relevant settings to what the user requests, extract the relevant
characteristics, and then restore the ``C'' numeric locale. characteristics, and then restore the \samp{C} numeric locale.
When Python code uses the \module{locale} module to change the locale, When Python code uses the \module{locale} module to change the locale,
this also affect the embedding application. If the embedding this also affect the embedding application. If the embedding

21
Doc/liblocale.tex
View file

@ -203,7 +203,7 @@ implementation are broken in such a way that frequent locale changes
may cause core dumps. This makes the locale somewhat painful to use may cause core dumps. This makes the locale somewhat painful to use
correctly. correctly.
Initially, when a program is started, the locale is the "C" locale, no Initially, when a program is started, the locale is the \samp{C} locale, no
matter what the user's preferred locale is. The program must matter what the user's preferred locale is. The program must
explicitly say that it wants the user's preferred locale settings by explicitly say that it wants the user's preferred locale settings by
calling \code{setlocale(LC_ALL, "")}. calling \code{setlocale(LC_ALL, "")}.
@ -219,8 +219,8 @@ independent version of an operation that is affected by the locale
\function{time.strftime()})), you will have to find a way to do it \function{time.strftime()})), you will have to find a way to do it
without using the standard library routine. Even better is convincing without using the standard library routine. Even better is convincing
yourself that using locale settings is okay. Only as a last resort yourself that using locale settings is okay. Only as a last resort
should you document that your module is not compatible with non-C should you document that your module is not compatible with
locale settings. non-\samp{C} locale settings.
The case conversion functions in the The case conversion functions in the
\module{string}\refstmodindex{string} and \module{string}\refstmodindex{string} and
@ -240,30 +240,31 @@ is to use the special functions defined by this module:
\function{str()}. \function{str()}.
\subsection{For extension writers and programs that embed Python} \subsection{For extension writers and programs that embed Python}
\label{embedding-locale}
Extension modules should never call \function{setlocale()}, except to Extension modules should never call \function{setlocale()}, except to
find out what the current locale is. But since the return value can find out what the current locale is. But since the return value can
only be used portably to restore it, that is not very useful (except only be used portably to restore it, that is not very useful (except
perhaps to find out whether or not the locale is ``C''). perhaps to find out whether or not the locale is \samp{C}).
When Python is embedded in an application, if the application sets the When Python is embedded in an application, if the application sets the
locale to something specific before initializing Python, that is locale to something specific before initializing Python, that is
generally okay, and Python will use whatever locale is set, generally okay, and Python will use whatever locale is set,
\strong{except} that the \constant{LC_NUMERIC} locale should always be \emph{except} that the \constant{LC_NUMERIC} locale should always be
``C''. \samp{C}.
The \function{setlocale()} function in the \module{locale} module contains The \function{setlocale()} function in the \module{locale} module contains
gives the Python progammer the impression that you can manipulate the gives the Python progammer the impression that you can manipulate the
\constant{LC_NUMERIC} locale setting, but this not the case at the C \constant{LC_NUMERIC} locale setting, but this not the case at the \C{}
level: C code will always find that the \constant{LC_NUMERIC} locale level: \C{} code will always find that the \constant{LC_NUMERIC} locale
setting is ``C''. This is because too much would break when the setting is \samp{C}. This is because too much would break when the
decimal point character is set to something else than a period decimal point character is set to something else than a period
(e.g. the Python parser would break). Caveat: threads that run (e.g. the Python parser would break). Caveat: threads that run
without holding Python's global interpreter lock may occasionally find without holding Python's global interpreter lock may occasionally find
that the numeric locale setting differs; this is because the only that the numeric locale setting differs; this is because the only
portable way to implement this feature is to set the numeric locale portable way to implement this feature is to set the numeric locale
settings to what the user requests, extract the relevant settings to what the user requests, extract the relevant
characteristics, and then restore the ``C'' numeric locale. characteristics, and then restore the \samp{C} numeric locale.
When Python code uses the \module{locale} module to change the locale, When Python code uses the \module{locale} module to change the locale,
this also affect the embedding application. If the embedding this also affect the embedding application. If the embedding