On 24/07/2005, at 4:20 PM, Bob Ippolito wrote:
> I fixed this problem for 2.4.1 (CVS HEAD should be fine too). I
> don't really consider 2.3 important enough to spend my time
> backporting. If you notice, Apple didn't compile Python 2.3 under
> gcc 4 either.
Great. As long as its fixed th
I was looking at the MacPython installer (2.4.1) and it's not clear
if Xcode is needed. Other than not being able to build modules from
C source, I noticed one bit that is installed in the System python
framework, PantherPythonFix, that has some reference to GCC. There's
nothing in the in
On Jul 24, 2005, at 7:28 AM, William K wrote:
> I was looking at the MacPython installer (2.4.1) and it's not clear
> if Xcode is needed. Other than not being able to build modules from
> C source, I noticed one bit that is installed in the System python
> framework, PantherPythonFix, that has s
On 24/07/2005, at 4:20 PM, Bob Ippolito wrote:
>
> I fixed this problem for 2.4.1 (CVS HEAD should be fine too). I
> don't really consider 2.3 important enough to spend my time
> backporting. If you notice, Apple didn't compile Python 2.3 under
> gcc 4 either.
I got a chance to look at the
On Jul 24, 2005, at 2:43 PM, Bill Northcott wrote:
> On 24/07/2005, at 4:20 PM, Bob Ippolito wrote:
>
>>
>> I fixed this problem for 2.4.1 (CVS HEAD should be fine too). I
>> don't really consider 2.3 important enough to spend my time
>> backporting. If you notice, Apple didn't compile Pyth
On 25/07/2005, at 10:46 AM, Bob Ippolito wrote:
> The fix was simply to get it to compile, and was done way before
> the x86 transition. Changing the build process is a PITA and you
> have to be careful not to cause issues with other platforms and
> previous versions of OS X.
>
> Patches ac
