iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Some changes in wording, and a different division 

as discussed with Greg Ward <gward@mems-exchange.org>.
This commit is contained in:
Moshe Zadka 2000-08-11 03:54:16 +00:00
parent 8943f419a9
commit 2a6b638168
1 changed files with 24 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

35
pep-0206.txt
View File

@ -35,21 +35,34 @@ Batteries Included Philosophy
The Proposed Solution
The proposed solution is to download a few important third-party
libraries, and distribute them with the source distribution of
Python. In addition, the build procedure will be changed to build
those libraries by default, and build the Python modules which
rely on them linked against those libraries. Individual users
will still be able to link the Python modules against already
The proposed solution is to maintain an alternate form of distribution,
nicknamed the "sumo" interpreter. It will be structured as a core
interpreter + extra useful libraries. In addition, the build procedure
will be changed to build those libraries by default, and build the Python
modules which rely on them linked against those libraries. Individual
users will still be able to link the Python modules against already
installed libraries, or disable them completely.
Additionally, some Open Source third-party Python modules will
also be distributed together with the source distribution. The
difference between those and external libraries is that the latter
also be distributed in the "sumo" distribution. The
difference between those and external libraries is that the former
are distributed in order to make the Python distribution self
contained, and the former are added so there will be new
contained, and the latter are added so there will be new
functionality in out-of-the-box Python.
Python Advanced Library
Since it is decided that the additions to the interpreter will live
in a seperate directory, they can even be distributed seperately,
as an additional library. This is called the "Python Advanced Library",
or PAL. This will also solve the problem of an advanced library module
failing -- the core interpreter will still be built, tested and installed.
Since the compilation of the other modules be helped by Python scripts,
it is quite possible that it will even install as many modules as it
can.
Suggested Libraries and Modules
Here is the tentative list of libraries which are proposed to be
dealt with in this manner, and where they can be downloaded:
@ -88,7 +101,7 @@ Software covered by the GNU Public License
While many Python modules rely on software distributed under the
GNU General Public License and the GNU Lesser General Public
License, no such sources are proposed here to be added to the
Python interpreter. Currently, the Python interpreter is
sumo interpreter. Currently, the Python interpreter is
distributed under a closed-source-friendly license, which means
that it is possible to include it in a closed source product.
Making redistributers worry about which parts they need to remove
@ -102,7 +115,7 @@ Open Issues
What should the build procedure look like?
What to do if compilation of a supporting library fails?
How are the additional modules tested?
ESR also mentioned libpng, but I don't know of a Python module
that uses it.