On Feb 3, 2006, at 5:29 PM, Bill Northcott wrote: > On 04/02/2006, at 12:00 PM, Bob Ippolito wrote: >>> The issue only arises using Python 2.4.x on Tiger. It does not >>> arise >>> with Python 2.3.x on Tiger or Python 2.4.x on Panther (MacOS 10.3.x) >> >> On top of that, it should only happen if you're using a Python >> 2.4.x build on Tiger that was compiled on Panther. > > Why would it not happen if Python 2.4 was built on Tiger?
The configure script detects Mac OS X 10.4 and changes its behavior accordingly. All this POSIX compliance stuff was broken on Mac OS X 10.2, then Apple 'fixed' it in 10.3, but it regressed in 10.4 When 10.3 came out, a Python developer decided to turn on the POSIX compliance junk. When 10.4 came out, Guido's time machine was apparently unavailable. In my current branch for universal binaries, the configure script will once again assume Mac OS X is not POSIX compliant until proven otherwise... even if compiled on 10.3. >> This is exactly what TigerPython24Fix is for: >> http://undefined.org/python/#TigerPython24Fix > > As far as I can see this patch is a work around for the binary > package on Bob's web site. Kevin and I are trying to fix the > source code. so things build correctly without user level patching. The fix needs to happen in Python, not in wxPython. You MUST apply TigerPython24Fix if you expect to build ANY extensions with this Python 2.4.1 build on OS X 10.4. That's just how it is. -bob _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
