mirrors/cpython
1
0
Fork 0
mirror of https://github.com/python/cpython.git synced 2025-07-23 11:15:24 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 11

(finally) unified the interpreter and the applet as Just suggested ages ago. The

Browse source 
resulting program is called PythonInterpreter.
This commit is contained in:
Jack Jansen 1999-02-14 23:12:06 +00:00
parent f32834c206
commit 3b8052685c
5 changed files with 7 additions and 14 deletions
Download patch file Download diff file Expand all files Collapse all files

BIN
Mac/Build/PythonApplet.prj
View file

Binary file not shown.

BIN
Mac/Build/Python.prj → Mac/Build/PythonInterpreter.prj
View file

Binary file not shown.

16
Mac/Demo/building.html
View file

@ -346,8 +346,8 @@ it from the system folder and running Python once again will re-create it.
First you optionally build the external libraries with buildlibs.prj. Next, First you optionally build the external libraries with buildlibs.prj. Next,
the projects for the projects for
interpreter, core library and applet skeleton are all linked together, so interpreter, core library and applet skeleton are all linked together, so
building the fat targets in <code>Python.prj</code> and building the fat target in <code>PythonEngine.prj</code>
<code>PythonApplet.prj</code> will result in everything being built. The will result in everything being built. The
resulting applications and fat shared library are deposited in the main resulting applications and fat shared library are deposited in the main
Python folder. Finally, you build all the plugins with the plugins.prj project. Python folder. Finally, you build all the plugins with the plugins.prj project.
@ -364,16 +364,10 @@ moving the file will cause you grief later if you rebuild the library and
forget to copy it to the extensions folder again. The InstallPython applet forget to copy it to the extensions folder again. The InstallPython applet
will also do this, along with creating the plugin aliases. will also do this, along with creating the plugin aliases.
<DT> Python <DT> PythonInterpeter
<DD> The interpreter. This is basically a routine to call out to the <DD> The interpreter. This is basically a routine to call out to the
shared library. <p> shared library. Unlike in previous releases the same program is used for
creating applets (for which formerly PythonApplet was used). <p>
<DT> PythonAppletPPC
<DD> The applet skeleton application. Very similar to
<code>PythonPPC</code>, but it calls to a different entrypoint in the
core library. The <code>mkapplet</code> script will copy this complete
file, and add a <code>'PYC '</code> with the module to generate an
applet. <p>
<DT> Plugin projects <DT> Plugin projects
<DD> Each plugin module has a separate project. The <code>Plugins.prj</code> <DD> Each plugin module has a separate project. The <code>Plugins.prj</code>

2
Mac/Lib/buildtools.py
View file

@ -22,7 +22,7 @@ DEBUG=1
MAGIC = imp.get_magic() MAGIC = imp.get_magic()
# Template file (searched on sys.path) # Template file (searched on sys.path)
TEMPLATE = "PythonApplet" TEMPLATE = "PythonInterpreter"
# Specification of our resource # Specification of our resource
RESTYPE = 'PYC ' RESTYPE = 'PYC '

3
Mac/scripts/fullbuild.py
View file

@ -149,8 +149,7 @@ def handle_dialog(filename):
BUILD_DICT = { BUILD_DICT = {
I_CORE : (buildmwproject, "CWIE", [ I_CORE : (buildmwproject, "CWIE", [
(":Mac:Build:PythonCore.prj", "PythonCore"), (":Mac:Build:PythonCore.prj", "PythonCore"),
(":Mac:Build:Python.prj", "PythonFAT"), (":Mac:Build:PythonInterpreter.prj", "PythonInterpreter"),
(":Mac:Build:PythonApplet.prj", "PythonAppletFAT"),
]), ]),
I_PPC_PLUGINS : (buildmwproject, "CWIE", [ I_PPC_PLUGINS : (buildmwproject, "CWIE", [