[Pythonmac-SIG] SIOUX Console ( was sys.exit )

[Alexandre Parenteau]

Jack,

> On Wednesday, January 30, 2002, at 06:42  PM, Alexandre Parenteau wrote:
>> [unrelated] Jack, I understand why you put it inside #ifdef
>> USE_GUSI2 but it
>> forces us to have the GUSI2 header externally, whereas in
>> theory we would
>> not have to use GUSI in order to use for the Python SDK.
> 
> You'll have to explain what you mean here, "forces us to have
> the GUSI2 header externally".

Let say I want to use MacPython embedded in an application Y. When I compile
Y, I don't have necessarily to use GUSI 1 or 2. I can use MSL instead or
anything else (it is not completely true because if I end-up using another
C-library for Y, I may not be able to pass a FILE object to Python).

If I don't use GUSI in Y, USE_GUSI2 is false and the console handlers
functions are not exported by the headers of MacPython. However the console
symbols are very much in the shared library of MacPython and I can use them
from Y even if I don't use GUSI in Y. That is why it is logical to
encapsulate the console handlers with USE_GUSI2 only when building
MacPython. If the headers are used externally to MacPython, I should be
defined every time in the MacPython headers since MacPython is built with
GUSI2.

>> [unrelated] About a SDK, I regret we don't have PEF stub library and a
>> dedicated folder that we could copy at once to write
>> components. Something
>> like Python2.2/SDF/Headers, Python2.2/SDF/Headers/Mac,
>> Python2.2/SDF/Libraries, Python2.2/SDF/Resources.
> 
> Again, you have to explain, I understand neither what you're
> trying to accomplish, nor how:-)

I try to still embed MacPython in the application Y. I like to embed, it's
me... :-)

I'd like to have a MacPython SDK folder. If I'm interested only in making
compiled components to Python, it is handy to get the minimal set of Headers
and Libraries for doing so. Having a stub library is part of the "nice"
thing.

Alex.