On Feb 9, 2005, at 20:55, Richard Jones wrote:
On 10/02/2005, at 12:38 PM, Bob Ippolito wrote:I tried to reproduce this problem by dropping your Python dylib into my framework, and it worked fine.. what version of Mac OS X are you using and have you tried it a second time after killing build and dist?
That was it - I needed to clean out the old cruft (I had deleted dist, but not build). All better now.
Well, almost. Now I have an ominuous "socket.error: AF_UNIX path too long" to deal with :)
The man page for bind() says that I'll get this if the name is longer than NAME_MAX. Grep'ing /usr/include (the only place I know to look ;) gets me a value of 255 for NAME_MAX in <sys/syslimits.h> (there's some others, but I think that's the appropriate one.
The path is "/Users/richard/src/cg/CGPublisher-Zope/dist/CGPublisher-Zope.app/ Contents/Resources/runtime/zope-8000/zopectlsock.5345" which is clearly 118 chars long. So I'm a little confused. I need to go get some lunch, then I'll have another go at the problem :)
You should never, ever, ever, ever, ever write inside of a bundle anyway. You should make this runtime directory in /tmp, /Library/Application Support/, etc.
In fact, I was thinking that I should chmod -R g-w the contents of the app bundle a couple hours ago :)
See "Where To Put Application Files" in http://developer.apple.com/documentation/MacOSX/Conceptual/ BPFileSystem/index.html
See
_______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
