diff options
Diffstat (limited to 'Doc/library')
| -rw-r--r-- | Doc/library/calendar.rst | 12 | ||||
| -rw-r--r-- | Doc/library/locale.rst | 2 | ||||
| -rw-r--r-- | Doc/library/multiprocessing.rst | 2 | ||||
| -rw-r--r-- | Doc/library/threading.rst | 6 |
4 files changed, 14 insertions, 8 deletions
diff --git a/Doc/library/calendar.rst b/Doc/library/calendar.rst index 2228920..c8dac49 100644 --- a/Doc/library/calendar.rst +++ b/Doc/library/calendar.rst @@ -170,9 +170,9 @@ it's the base calendar for all computations. .. class:: LocaleTextCalendar(firstweekday=0, locale=None) This subclass of :class:`TextCalendar` can be passed a locale name in the - constructor and will return month and weekday names in the specified - locale. If this locale includes an encoding all strings containing month and - weekday names will be returned as unicode. + constructor and will return month and weekday names in the specified locale. + If this locale includes an encoding all strings containing month and weekday + names will be returned as unicode. .. class:: LocaleHTMLCalendar(firstweekday=0, locale=None) @@ -182,6 +182,12 @@ it's the base calendar for all computations. locale. If this locale includes an encoding all strings containing month and weekday names will be returned as unicode. +.. note:: + + The :meth:`formatweekday` and :meth:`formatmonthname` methods of these two + classes temporarily change the current locale to the given *locale*. Because + the current locale is a process-wide setting, they are not thread-safe. + For simple text calendars this module provides the following functions. diff --git a/Doc/library/locale.rst b/Doc/library/locale.rst index b9c001f..601c949 100644 --- a/Doc/library/locale.rst +++ b/Doc/library/locale.rst @@ -39,7 +39,7 @@ The :mod:`locale` module defines the following exception and functions: If *locale* is omitted or ``None``, the current setting for *category* is returned. - :func:`setlocale` is not thread safe on most systems. Applications typically + :func:`setlocale` is not thread-safe on most systems. Applications typically start with a call of :: import locale diff --git a/Doc/library/multiprocessing.rst b/Doc/library/multiprocessing.rst index 264d432..c4ee87e 100644 --- a/Doc/library/multiprocessing.rst +++ b/Doc/library/multiprocessing.rst @@ -214,7 +214,7 @@ However, if you really do need to use some shared data then The ``'d'`` and ``'i'`` arguments used when creating ``num`` and ``arr`` are typecodes of the kind used by the :mod:`array` module: ``'d'`` indicates a double precision float and ``'i'`` indicates a signed integer. These shared - objects will be process and thread safe. + objects will be process and thread-safe. For more flexibility in using shared memory one can use the :mod:`multiprocessing.sharedctypes` module which supports the creation of diff --git a/Doc/library/threading.rst b/Doc/library/threading.rst index 2e36402..8b4babc 100644 --- a/Doc/library/threading.rst +++ b/Doc/library/threading.rst @@ -753,9 +753,9 @@ Currently, :class:`Lock`, :class:`RLock`, :class:`Condition`, Importing in threaded code -------------------------- -While the import machinery is thread safe, there are two key -restrictions on threaded imports due to inherent limitations in the way -that thread safety is provided: +While the import machinery is thread-safe, there are two key restrictions on +threaded imports due to inherent limitations in the way that thread-safety is +provided: * Firstly, other than in the main module, an import should not have the side effect of spawning a new thread and then waiting for that thread in |