[Pythonmac-SIG] making plug-ins?

Jack Jansen Jack.Jansen@cwi.nl
Wed, 10 Feb 1999 22:41:14 +0100


Mac:Demo:plugins.html is outdated, I'll be updating it. The missing
xxmodule.c file is a rather unfortunate side-effect of the way I build 
distributions, I'll try and remember to see if I can do something
about it for the next release. You don't need a source distribution
anymore, despite what the documentation says, loading the plugin
developer kit in the binary distribution is good enough. But, indeed,
you miss the xxmodule.c and xx.prj.exp files:-(

And if people are willing to "adopt" various of the neat extension
modules out there for MacPython I would be much obliged. As of the
next release the shared library CFM version numbering scheme should
finally allow extension modules to be written for multiple Python
versions, so that should make it easier to distribute binary plugin
modules. For the CFM-wise: the "current" cfm version will be the same
as sys.hexversion of the current Python, and the "oldest" cfm version
will be sys.hexversion of the oldest Python that has the same
PYTHON_API_VERSION as the current Python (unless MetroWerks change
their C library in between, in which case it'll be the sys.hexversion
of the oldest Python built with a compatible C library). If I can work 
out how to keep only the definition part of a .slb I might also try
including that slb of the oldest PythonCore with the same
PYTHON_API_VERSION, then extension-builders can link against that and
create an extension module that they know (well... be reasonably
sure:-) will run in older Pythons as well.
--
Jack Jansen             | ++++ stop the execution of Mumia Abu-Jamal ++++
Jack.Jansen@cwi.nl      | ++++ if you agree copy these lines to your sig ++++
http://www.cwi.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm