Re: [Pythonmac-SIG] universal binary installer, take 1

Hi there. I just joined the list, and I noticed you're looking for feedback on the new universal binary. I haven't read all of the archives, but if there's anything specific you want tested, let me know. Meanwhile, here's what I've done: I installed the universal 2.4 on an Intel iMac, built Psyco

Re: [Pythonmac-SIG] resizing terminal and curses

> Terminal.app behaives particularly strangely - crashing when the > window is enlarged for the second time (xterm crashes immediately), > though not the first For me, it crashes in Terminal.app the first time I try to enlarge the window, not the second. I see no difference between Terminal and xt

[Pythonmac-SIG] Questions about various bits of Intel status

I'm guessing these answers are all out there somewhere, but I can't find them. So I apologize if I'm being stupid, but: First, what's up with ctypes and other things that need libffi? They complain that it hasn't been ported to darwin x86 and punt. The latest information I could find was a blog at

Re: [Pythonmac-SIG] Questions about various bits of Intel status

Thanks for the quick answers, and it's good to know that I'm not missing information right in front of my face Me: > > First, what's up with ctypes and other things that > > need libffi? Ronald: > PyObjC contains a port of libffi to darwin/x86, but sadly > enough I didn't pay enough attentio

Re: [Pythonmac-SIG] Questions about various bits of Intel status

Andrew Barnert: > > What are the actual problems with having a root/wheel > > 755 framework directory instead of root/admin 775? I > > guess it means you can't install modules to > > site-packages out of .pkg files? If it's important, it > > would be nice i

Re: [Pythonmac-SIG] [ann] Appscript Installer 1.3 released

It might be worth putting up something visible anyway. Right now, if you have an Intel Mac, you don't want to/know how to compile Python yourself, and you don't search the archives of this list, your only choices are ActiveState, Darwinports (non-framework, and other issues), or Fink (completely

[Pythonmac-SIG] Two appscript problems, plus a stupid question

If this list is the wrong place, I apologize; just let me know and I'll ask in the right place. Otherwise: Now that I can use appscript with Python 2.4 on my Intel box, I've been going back over some of my iTunes-controlling scripts, and I've run into two problems and one stupid question. First,

[Pythonmac-SIG] Building extension modules with Xcode 5

If you use a binary installer of Python 2.7.5, 3.3.2, or 3.4.0a4 from python.org on either 10.8 or 10.9, and you have Xcode 5, you can't build any C extension modules, because you don't have a compiler named "gcc-4.2". What should users be doing until this is fixed? The workaround that everyone

[Pythonmac-SIG] Building redistributable binaries with Xcode 4.4+

There's a related issue, using the 10.6 SDK. This one is over a year old, but as far as I know still has no solution. Xcode 4.4+ have no 10.6 SDK. This doesn't actually stop you from building extensions; they just falls back to building for your machine when it can't find the SDK. But that mean

Re: [Pythonmac-SIG] Building extension modules with Xcode 5

> From: Kevin Walzer > Sent: Thursday, October 24, 2013 6:14 PM > > On 10/24/13 7:50 PM, Andrew Barnert wrote: >> What should users be doing until this is fixed? > > Build Python yourself, in my view. Python is one of the easiest scripting > languages to build. And

Re: [Pythonmac-SIG] Building extension modules with Xcode 5

looking for gcc-4.2. If I do any other sequence, it always succeeds. I'll keep trying to figure out the repro case. Sent from a random iPhone On Oct 24, 2013, at 19:29, Ned Deily wrote: > In article <1382665677.4566.yahoomail...@web184704.mail.ne1.yahoo.com>, > Andrew Barnert