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