[Python-checkins] CVS: python/nondist/peps pep-0206.txt,1.7,1.8
Moshe Zadka
python-dev@python.org
Thu, 10 Aug 2000 20:54:20 -0700
Update of /cvsroot/python/python/nondist/peps
In directory slayer.i.sourceforge.net:/tmp/cvs-serv16606
Modified Files:
pep-0206.txt
Log Message:
Some changes in wording, and a different division
as discussed with Greg Ward <gward@mems-exchange.org>.
Index: pep-0206.txt
===================================================================
RCS file: /cvsroot/python/python/nondist/peps/pep-0206.txt,v
retrieving revision 1.7
retrieving revision 1.8
diff -C2 -r1.7 -r1.8
*** pep-0206.txt 2000/07/29 10:11:19 1.7
--- pep-0206.txt 2000/08/11 03:54:16 1.8
***************
*** 36,54 ****
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
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
are distributed in order to make the Python distribution self
! contained, and the former are added so there will be new
functionality in out-of-the-box Python.
Here is the tentative list of libraries which are proposed to be
dealt with in this manner, and where they can be downloaded:
--- 36,67 ----
The Proposed Solution
! 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 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 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:
***************
*** 89,93 ****
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
distributed under a closed-source-friendly license, which means
that it is possible to include it in a closed source product.
--- 102,106 ----
GNU General Public License and the GNU Lesser General Public
License, no such sources are proposed here to be added to the
! 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.
***************
*** 103,107 ****
What should the build procedure look like?
! What to do if compilation of a supporting library fails?
ESR also mentioned libpng, but I don't know of a Python module
--- 116,120 ----
What should the build procedure look like?
! How are the additional modules tested?
ESR also mentioned libpng, but I don't know of a Python module