blob: a0f2d6324f6539e71d38858ed05df93ce057532b [file] [log] [blame]
Georg Brandl116aa622007-08-15 14:28:22 +00001.. _library-intro:
2
3************
4Introduction
5************
6
7The "Python library" contains several different kinds of components.
8
9It contains data types that would normally be considered part of the "core" of a
10language, such as numbers and lists. For these types, the Python language core
11defines the form of literals and places some constraints on their semantics, but
12does not fully define the semantics. (On the other hand, the language core does
13define syntactic properties like the spelling and priorities of operators.)
14
15The library also contains built-in functions and exceptions --- objects that can
16be used by all Python code without the need of an :keyword:`import` statement.
17Some of these are defined by the core language, but many are not essential for
18the core semantics and are only described here.
19
20The bulk of the library, however, consists of a collection of modules. There are
21many ways to dissect this collection. Some modules are written in C and built
22in to the Python interpreter; others are written in Python and imported in
23source form. Some modules provide interfaces that are highly specific to
24Python, like printing a stack trace; some provide interfaces that are specific
25to particular operating systems, such as access to specific hardware; others
26provide interfaces that are specific to a particular application domain, like
27the World Wide Web. Some modules are available in all versions and ports of
28Python; others are only available when the underlying system supports or
29requires them; yet others are available only when a particular configuration
30option was chosen at the time when Python was compiled and installed.
31
32This manual is organized "from the inside out:" it first describes the built-in
33data types, then the built-in functions and exceptions, and finally the modules,
34grouped in chapters of related modules. The ordering of the chapters as well as
35the ordering of the modules within each chapter is roughly from most relevant to
36least important.
37
38This means that if you start reading this manual from the start, and skip to the
39next chapter when you get bored, you will get a reasonable overview of the
40available modules and application areas that are supported by the Python
41library. Of course, you don't *have* to read it like a novel --- you can also
42browse the table of contents (in front of the manual), or look for a specific
43function, module or term in the index (in the back). And finally, if you enjoy
44learning about random subjects, you choose a random page number (see module
45:mod:`random`) and read a section or two. Regardless of the order in which you
Alexandre Vassalottie52e3782009-07-17 09:18:18 +000046read the sections of this manual, it helps to start with chapter
47:ref:`built-in-funcs`, as the remainder of the manual assumes familiarity with
48this material.
Georg Brandl116aa622007-08-15 14:28:22 +000049
50Let the show begin!
51