| 
									
										
										
										
											2007-08-15 14:28:22 +00:00
										 |  |  | .. _library-intro:
 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | ************
 | 
					
						
							|  |  |  | Introduction
 | 
					
						
							|  |  |  | ************
 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | The "Python library" contains several different kinds of components.
 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | It contains data types that would normally be considered part of the "core" of a
 | 
					
						
							|  |  |  | language, such as numbers and lists.  For these types, the Python language core
 | 
					
						
							|  |  |  | defines the form of literals and places some constraints on their semantics, but
 | 
					
						
							|  |  |  | does not fully define the semantics.  (On the other hand, the language core does
 | 
					
						
							|  |  |  | define syntactic properties like the spelling and priorities of operators.)
 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | The library also contains built-in functions and exceptions --- objects that can
 | 
					
						
							|  |  |  | be used by all Python code without the need of an :keyword:`import` statement.
 | 
					
						
							|  |  |  | Some of these are defined by the core language, but many are not essential for
 | 
					
						
							|  |  |  | the core semantics and are only described here.
 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | The bulk of the library, however, consists of a collection of modules. There are
 | 
					
						
							|  |  |  | many ways to dissect this collection.  Some modules are written in C and built
 | 
					
						
							|  |  |  | in to the Python interpreter; others are written in Python and imported in
 | 
					
						
							|  |  |  | source form.  Some modules provide interfaces that are highly specific to
 | 
					
						
							|  |  |  | Python, like printing a stack trace; some provide interfaces that are specific
 | 
					
						
							|  |  |  | to particular operating systems, such as access to specific hardware; others
 | 
					
						
							|  |  |  | provide interfaces that are specific to a particular application domain, like
 | 
					
						
							|  |  |  | the World Wide Web. Some modules are available in all versions and ports of
 | 
					
						
							|  |  |  | Python; others are only available when the underlying system supports or
 | 
					
						
							|  |  |  | requires them; yet others are available only when a particular configuration
 | 
					
						
							|  |  |  | option was chosen at the time when Python was compiled and installed.
 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | This manual is organized "from the inside out:" it first describes the built-in
 | 
					
						
							|  |  |  | data types, then the built-in functions and exceptions, and finally the modules,
 | 
					
						
							|  |  |  | grouped in chapters of related modules.  The ordering of the chapters as well as
 | 
					
						
							|  |  |  | the ordering of the modules within each chapter is roughly from most relevant to
 | 
					
						
							|  |  |  | least important.
 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | This means that if you start reading this manual from the start, and skip to the
 | 
					
						
							|  |  |  | next chapter when you get bored, you will get a reasonable overview of the
 | 
					
						
							|  |  |  | available modules and application areas that are supported by the Python
 | 
					
						
							|  |  |  | library.  Of course, you don't *have* to read it like a novel --- you can also
 | 
					
						
							|  |  |  | browse the table of contents (in front of the manual), or look for a specific
 | 
					
						
							|  |  |  | function, module or term in the index (in the back).  And finally, if you enjoy
 | 
					
						
							|  |  |  | learning about random subjects, you choose a random page number (see module
 | 
					
						
							|  |  |  | :mod:`random`) and read a section or two.  Regardless of the order in which you
 | 
					
						
							| 
									
										
											  
											
												Merged revisions 73995,74002,74005,74007-74008,74011,74019-74023 via svnmerge from
svn+ssh://pythondev@svn.python.org/python/trunk
........
  r73995 | vinay.sajip | 2009-07-13 07:21:05 -0400 (Mon, 13 Jul 2009) | 1 line
  Issue #6314: logging: Extra checks on the "level" argument in more places.
........
  r74002 | marc-andre.lemburg | 2009-07-13 16:23:49 -0400 (Mon, 13 Jul 2009) | 6 lines
  Use a new global DEV_NULL instead of hard-coding /dev/null into the system
  command helper functions.
  See #6479 for some motivation.
........
  r74005 | marc-andre.lemburg | 2009-07-13 17:28:33 -0400 (Mon, 13 Jul 2009) | 6 lines
  Use a different VER command output parser to address the localization
  issues mentioned in #3410.
  Prepare for Windows 7 (still commented out).
........
  r74007 | michael.foord | 2009-07-14 13:58:12 -0400 (Tue, 14 Jul 2009) | 1 line
  Move TestRunner initialisation into unittest.TestProgram.runTests. Fixes issue 6418.
........
  r74008 | benjamin.peterson | 2009-07-14 20:46:42 -0400 (Tue, 14 Jul 2009) | 1 line
  update year
........
  r74011 | ezio.melotti | 2009-07-15 13:07:04 -0400 (Wed, 15 Jul 2009) | 1 line
  methods' names pep8ification
........
  r74019 | amaury.forgeotdarc | 2009-07-15 17:29:27 -0400 (Wed, 15 Jul 2009) | 2 lines
  #6076 Add a title to the IDLE Preferences window.
........
  r74020 | georg.brandl | 2009-07-16 03:18:07 -0400 (Thu, 16 Jul 2009) | 1 line
  #5910: fix kqueue for calls with more than one event.
........
  r74021 | georg.brandl | 2009-07-16 03:33:04 -0400 (Thu, 16 Jul 2009) | 1 line
  #6486: start with built in functions rather than "built in objects".
........
  r74022 | georg.brandl | 2009-07-16 03:38:35 -0400 (Thu, 16 Jul 2009) | 1 line
  #6481: fix typo in os.system() replacement.
........
  r74023 | jesse.noller | 2009-07-16 10:23:04 -0400 (Thu, 16 Jul 2009) | 1 line
  Issue 6433: multiprocessing.pool.map hangs on empty list
........
											
										 
											2009-07-17 09:18:18 +00:00
										 |  |  | read the sections of this manual, it helps to start with chapter
 | 
					
						
							|  |  |  | :ref:`built-in-funcs`, as the remainder of the manual assumes familiarity with
 | 
					
						
							|  |  |  | this material.
 | 
					
						
							| 
									
										
										
										
											2007-08-15 14:28:22 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  | Let the show begin!
 | 
					
						
							|  |  |  | 
 |