cpython

History

Fred Drake 3176b08874 Update to use more modern calling conventions; also avoid a magic number in the function table. Add a docstring for the function as well, since examples should show good form.		2001-11-17 06:30:20 +00:00
..
.cvsignore	import -> importexc	2001-02-20 20:54:09 +00:00
Makefile	Bump the version number; used to identify the Python runtime we link to.	2001-11-17 06:28:08 +00:00
README	…
demo.c	Update to use more modern calling conventions; also avoid a magic number	2001-11-17 06:30:20 +00:00
importexc.c	import.c -> importexc.c	2001-02-20 20:54:28 +00:00
loop.c	Slight reworking to make it more useful for debugging	2001-01-23 16:42:01 +00:00

README

This directory show how to embed the Python interpreter in your own
application.  The file demo.c shows you all that is needed in your C
code.

To build it, you may have to edit the Makefile:

1) set blddir to the directory where you built Python, if it isn't in
the source directory (../..)

2) change the variables that together define the list of libraries
(MODLIBS, LIBS, SYSLIBS) to link with, to match their definitions in
$(blddir)/Modules/Makefile

An additional test program, loop.c, is used to experiment with memory
leakage caused by repeated initialization and finalization of the
interpreter.  It can be build by saying "make loop" and tested with
"make looptest".  Command line usage is "./loop <python-command>",
e.g. "./loop 'print 2+2'" should spit out an endless number of lines
containing the number 4.