From: David Cortesi <davecortesi@gm...> - 2011-04-21 23:33:32
OK, I reported an error attempting to install pyobjc 2.3 on Mac OS 10.6.
Div Shekhar pointed out that 2.2b3 is already there! Whoa, so it is. Thank you.
However when running some of the PyGui tests I get an error that Greg
Ewing finds mysterious, and which might be related to the use of
pyobjc 2.2, whereas 2.3 is supposedly required by PyGUI.
(Specifically, test 22 and 28 give "UninitializedDeallocWarning:
leaking an uninitialized object of type NSBitmapImageRep")
So I repeated my attempts to install 2.3. First I installed the latest
version of XCode (3.2.6) (4.1 gig download, sheesh). Then ran
sudo easy_install pyobjc
with the same result as before (see earlier in this thread).
Everything perks along fine through the following modules:
pyobjc-framework-SystemConfiguration (produces a lot of C warnings)
and then it hits pyobjc-framework-ScreenSaver
there are a lot of C warnings and a couple of errors, then:
lipo: can't open input file: /var/tmp//ccWUi61Z.out (No such file or directory)
error: Setup script exited with error: command 'gcc-4.2' failed with
exit status 1
Now, 1, this is the first appearance of "lipo" in the install dialog,
and B, that path /var/tmp and two consecutive slashes can't be
There is something wrong with that install sequence. I'd appreciate
any guidance on how to get around it.
Thanks for your time,
David Cortesi wrote:
> So I repeated my attempts to install 2.3. First I installed the latest
> version of XCode (3.2.6) (4.1 gig download, sheesh). Then ran
> sudo easy_install pyobjc
> and then it hits pyobjc-framework-ScreenSaver
> there are a lot of C warnings and a couple of errors, then:
> lipo: can't open input file: /var/tmp//ccWUi61Z.out (No such file or directory)
> error: Setup script exited with error: command 'gcc-4.2' failed with
> exit status 1
PyGUI doesn't actually need all of the sub-packages of PyObjC,
all it needs is 'pyobjc_core' and 'pyobjc_framework_Cocoa'.
PyPI doesn't make it easy, but you can get to the sub-packages
individually this way:
I didn't even attempt to use easy_install (I don't like setuptools
and will try to avoid touching it if at all possible). If I
remember correctly, I downloaded the .egg files, unzipped them and
manually moved their contents into site-packages.
I don't think you should need to have Xcode installed to do any
To the PyObjC developers, I would make the following requests:
1) Please DON'T require setuptools or easy-install. Make it available
either as a standard MacOSX installer package or an ordinary Python
package that can be installed using 'python setup.py install'.
2) Make the individual packages easily findable, downloadable
and installable separately for those that don't need the whole