summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAntoine Pitrou <solipsis@pitrou.net>2011-01-06 16:34:50 (GMT)
committerAntoine Pitrou <solipsis@pitrou.net>2011-01-06 16:34:50 (GMT)
commit6e7d711d2a54087051e215f85115528a346c25d1 (patch)
tree7811fd8882e7e3258c1017daebded9f5c70625b2
parent818581c72a4f93fe0462072dad8440d57a06cd1d (diff)
downloadcpython-6e7d711d2a54087051e215f85115528a346c25d1.zip
cpython-6e7d711d2a54087051e215f85115528a346c25d1.tar.gz
cpython-6e7d711d2a54087051e215f85115528a346c25d1.tar.bz2
Merged revisions 87792 via svnmerge from
svn+ssh://pythondev@svn.python.org/python/branches/py3k ........ r87792 | antoine.pitrou | 2011-01-06 17:31:28 +0100 (jeu., 06 janv. 2011) | 3 lines Elaborate about the GIL. ........
-rw-r--r--Doc/glossary.rst36
-rw-r--r--Doc/library/threading.rst11
2 files changed, 34 insertions, 13 deletions
diff --git a/Doc/glossary.rst b/Doc/glossary.rst
index 377f678..881831d 100644
--- a/Doc/glossary.rst
+++ b/Doc/glossary.rst
@@ -99,9 +99,10 @@ Glossary
See :pep:`343`.
CPython
- The canonical implementation of the Python programming language. The
- term "CPython" is used in contexts when necessary to distinguish this
- implementation from others such as Jython or IronPython.
+ The canonical implementation of the Python programming language, as
+ distributed on `python.org <http://python.org>`_. The term "CPython"
+ is used when necessary to distinguish this implementation from others
+ such as Jython or IronPython.
decorator
A function returning another function, usually applied as a function
@@ -258,16 +259,25 @@ Glossary
See :term:`global interpreter lock`.
global interpreter lock
- The lock used by Python threads to assure that only one thread
- executes in the :term:`CPython` :term:`virtual machine` at a time.
- This simplifies the CPython implementation by assuring that no two
- processes can access the same memory at the same time. Locking the
- entire interpreter makes it easier for the interpreter to be
- multi-threaded, at the expense of much of the parallelism afforded by
- multi-processor machines. Efforts have been made in the past to
- create a "free-threaded" interpreter (one which locks shared data at a
- much finer granularity), but so far none have been successful because
- performance suffered in the common single-processor case.
+ The mechanism used by the :term:`CPython` interpreter to assure that
+ only one thread executes Python :term:`bytecode` at a time.
+ This simplifies the CPython implementation by making the object model
+ (including critical built-in types such as :class:`dict`) implicitly
+ safe against concurrent access. Locking the entire interpreter
+ makes it easier for the interpreter to be multi-threaded, at the
+ expense of much of the parallelism afforded by multi-processor
+ machines.
+
+ However, some extension modules, either standard or third-party,
+ are designed so as to release the GIL when doing computationally-intensive
+ tasks such as compression or hashing. Also, the GIL is always released
+ when doing I/O.
+
+ Past efforts to create a "free-threaded" interpreter (one which locks
+ shared data at a much finer granularity) have not been successful
+ because performance suffered in the common single-processor case. It
+ is believed that overcoming this performance issue would make the
+ implementation much more complicated and therefore costlier to maintain.
hashable
An object is *hashable* if it has a hash value which never changes during
diff --git a/Doc/library/threading.rst b/Doc/library/threading.rst
index c9ef294..efb0476 100644
--- a/Doc/library/threading.rst
+++ b/Doc/library/threading.rst
@@ -17,6 +17,17 @@ The :mod:`dummy_threading` module is provided for situations where
methods and functions in this module in the Python 2.x series are still
supported by this module.
+.. impl-detail::
+
+ Due to the :term:`Global Interpreter Lock`, in CPython only one thread
+ can execute Python code at once (even though certain performance-oriented
+ libraries might overcome this limitation).
+ If you want your application to make better of use of the computational
+ resources of multi-core machines, you are advised to use
+ :mod:`multiprocessing`. However, threading is still an appropriate model
+ if you want to run multiple I/O-bound tasks simultaneously.
+
+
This module defines the following functions and objects: