[ python-Bugs-856387 ] PyMac_GetOSErrException hack for 2.3.0 compatibility?

[SourceForge.net]

Bugs item #856387, was opened at 2003-12-08 20:07
Message generated for change (Comment added) made by jackjansen
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=856387&group_id=5470

Category: Macintosh
Group: Feature Request
Status: Open
Resolution: None
Priority: 1
Submitted By: Bob Ippolito (etrepum)
Assigned to: Jack Jansen (jackjansen)
Summary: PyMac_GetOSErrException hack for 2.3.0 compatibility?

Initial Comment:
I'd like to be able to backport modules from Python CVS to 
2.3.0, such as _Launch, without changing source if 
possible.  The older pymactoolbox.h did not have 
PyMac_GetOSErrException.  I guess this was in macglue.h 
previously?  distutils always puts the installed Python's 
include dir first, so I can't use my CVS include dir.  Would it 
be reasonable to put a hack in the sources for these modules 
such that they can work around the pymactoolbox.h 
differences, or should I replace my system pymactoolbox.h?

----------------------------------------------------------------------

>Comment By: Jack Jansen (jackjansen)
Date: 2003-12-09 13:20

Message:
Logged In: YES 
user_id=45365

Coming to think of it: the solution of moving the definition to 
pymactoolbox.h isn't good enough for distributing source modules 
to Python 2.3.0, which we also want.

I will adapt the sources to compile both under 2.3.0 and 2.4.

----------------------------------------------------------------------

Comment By: Jack Jansen (jackjansen)
Date: 2003-12-08 20:53

Message:
Logged In: YES 
user_id=45365

Including macglue.h will also include pymactoolbox.h, so moving 
the declaration there in 2.3maint looks safe enough (and, indeed, 
it should have been there in the first place).

----------------------------------------------------------------------

Comment By: Bob Ippolito (etrepum)
Date: 2003-12-08 20:47

Message:
Logged In: YES 
user_id=139309

This is the method I'm currently using:
I have a folder build_launch sitting next to my checkout of Python 
CVS.  In it, I have a folder src/launch that was cp -r'ed from the 
Python CVS tree.  Also inside src/launch, I have symlink to ../../../
python/dist/src/Include/pythonmac.h.  This builds correctly, as the 
additions to pythonmac.h reflect functions that are actually 
exported from the Python.framework, but were not in the older 
version of pythonmac.h.

This seems to work alright, because I can still (separately though) 
cvs up in my copied launch folder, and the pythonmac.h will be 
updated whenever I cvs up python.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=856387&group_id=5470