forked from python/peps
/
pep-0206.txt
128 lines (84 loc) · 3.26 KB
/
pep-0206.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
PEP: 206
Title: Python Advanced Library
Version: $Revision$
Last-Modified: $Date$
Author: A.M. Kuchling <amk@amk.ca>
Status: Withdrawn
Type: Informational
Content-Type: text/x-rst
Created: 14-Jul-2000
Post-History:
Introduction
============
This PEP describes the Python Advanced Library, a collection of
high-quality and frequently-used third party extension modules.
Batteries Included Philosophy
=============================
The Python source distribution has long maintained the philosophy
of "batteries included" -- having a rich and versatile standard
library which is immediately available, without making the user
download separate packages. This gives the Python language a head
start in many projects.
However, the standard library modules aren't always the best
choices for a job. Some library modules were quick hacks
(e.g. ``calendar``, ``commands``), some were designed poorly and are now
near-impossible to fix (``cgi``), and some have been rendered obsolete
by other, more complete modules (``binascii`` offers the same features
as the ``binhex``, ``uu``, ``base64`` modules). This PEP describes a list of
third-party modules that make Python more competitive for various
application domains, forming the Python Advanced Library.
The deliverable is a set of scripts that will retrieve, build, and
install the packages for a particular application domain. The
Python Package Index now contains enough information to let
software automatically find packages and download them, so the
time is ripe to implement this.
Currently this document doesn't suggest *removing* modules from
the standard library that are superseded by a third-party module.
That's difficult to do because it entails many backward-compatibility
problems, so it's not worth bothering with now.
Please suggest additional domains of interest.
Domain: Web tasks
=================
XML parsing: ElementTree + SAX.
URL retrieval: libcurl? other possibilities?
HTML parsing: mxTidy? HTMLParser?
Async network I/O: Twisted
RDF parser: ???
HTTP serving: ???
HTTP cookie processing: ???
Web framework: A WSGI gateway, perhaps? Paste?
Graphics: PIL, Chaco.
Domain: Scientific Programming
==============================
Numeric: Numeric, SciPy
Graphics: PIL, Chaco.
Domain: Application Development
===============================
GUI toolkit: ???
Graphics: Reportlab for PDF generation.
Domain: Education
=================
Graphics: PyGame
Software covered by the GNU General Public License
==================================================
Some of these third-party modules are covered by the GNU General
Public License and the GNU Lesser General Public License.
Providing a script to download and install such packages, or even
assembling all these packages into a single tarball or CD-ROM,
shouldn't cause any difficulties with the GPL, under the "mere
aggregation" clause of the license.
Open Issues
===========
What other application domains are important?
Should this just be a set of Ubuntu or Debian packages? Compiling
things such as PyGame can be very complicated and may be too
difficult to automate.
Acknowledgements
================
The PEP is based on an earlier draft PEP by Moshe Zadka, titled
"2.0 Batteries Included."
..
Local Variables:
mode: indented-text
indent-tabs-mode: nil
End: