pyobjc-dev — CVS commit notices go here

Re: [Pyobjc-dev] memory leak

[Ronald O. <ron...@ma...>]

On 8 May, 2011, at 23:56, Greg Ewing wrote:

> Daniel Luis dos Santos wrote:
> 
>> 	string = NSString.alloc().init()
>> 
>> /Users/dlsa/code/cirrusstore/client/build/cirrusclient.app/Contents/Resources/menubaractions.py:44: UninitializedDeallocWarning: leaking an uninitialized object of type NSPlaceholderString
>>  string = NSString.alloc().init()
> 
> Python strings get converted to NSStrings automatically where
> needed, so is there some reason you can't use an empty Python
> string instead?

I don't know why Daniel wants to use an NSString, but there are reasons to use NSString instead of Python unicode strings, for example because NSString has a number of usefull methods with no easy native equivalent.

Ronald
> 
> -- 
> Greg
> 
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network 
> management toolset available today.  Delivers lowest initial 
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev

Re: [Pyobjc-dev] memory leak

[Ronald O. <ron...@ma...>]

On 8 May, 2011, at 19:51, Daniel Luis dos Santos wrote:

> Hello,
> 
> I have some python code in a pyobjc app. At some point I want to initialize a NSString :
> 
> 	string = NSString.alloc().init()

Which version of pyobjc do you use? This works for me:

>>> from Foundation import NSString
s = NSString.string>>> s = NSString.string()
>>> s
u''
>>> s = NSString.alloc().init()
>>> s
u''

The PyObjC version can be found using:   python -c 'import objc; print(objc.__version__)'

Ronald

> 
> In the terminal I get the following output :
> 
> /Users/dlsa/code/cirrusstore/client/build/cirrusclient.app/Contents/Resources/menubaractions.py:44: UninitializedDeallocWarning: leaking an uninitialized object of type NSPlaceholderString
>  string = NSString.alloc().init()
> 
> 
> I have in my objective C bootstrap code the creation of an Auto release pool.
> 
> If I try :
> 
> 	string = NSString.alloc().init().autorelease()
> 
> I get the same warning.
> 
> Why does this happen ?
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network 
> management toolset available today.  Delivers lowest initial 
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev

[Pyobjc-dev] PyObjC with PyInstaller

[Trevor B. <mr...@gm...>]

Hello,

I know this is more of a question for the PyInstaller mailing list, but
I wanted to check here and see if anyone has successfully used PyObjC
with PyInstaller?

I'm trying to create a PyInstaller package with PyTTSx (text-to-speech
module), which uses PyObjC, but it seems that some dynamic imports
related to the PyObjC "bridgesupport" module are failing.  The
PyInstaller package is made successfully, but I get the following
exception at runtime:

------------------------------
  File
"/Users/<path>/pyinstaller/test/build/pyi.darwin/test/outPYZ1.pyz/pyttsx.engine",
line 45, in __init__
  File
"/Users/<path>/pyinstaller/test/build/pyi.darwin/test/outPYZ1.pyz/pyttsx.driver",
line 64, in __init__
  File "/Users/<path>/pyinstaller/PyInstaller/iu.py", line 431, in
importHook
    mod = _self_doimport(nm, ctx, fqname)
...
... <lots of iu.py stuff>
...
  File
"/Users/<path>/pyinstaller/test/build/pyi.darwin/test/outPYZ1.pyz/CoreFoundation",
line 19, in <module>
  File
"/Users/<path>/pyinstaller/test/build/pyi.darwin/test/outPYZ1.pyz/objc._bridgesupport",
line 156, in initFrameworkWrapper
  File
"/Users/<path>/pyinstaller/test/build/pyi.darwin/test/outPYZ1.pyz/objc._bridgesupport",
line 58, in _parseBridgeSupport
ValueError: Don't know CF type for typestr '^{__CFAllocator=}', cannot
create special wrapper
------------------------------

Any information on this would help!  I'm willing to hack around dynamic
loading entirely if I can figure out a reasonable way.

Thanks,

Trevor

Re: [Pyobjc-dev] memory leak

[Greg E. <gre...@ca...>]

Daniel Luis dos Santos wrote:

> 	string = NSString.alloc().init()
> 
> /Users/dlsa/code/cirrusstore/client/build/cirrusclient.app/Contents/Resources/menubaractions.py:44: UninitializedDeallocWarning: leaking an uninitialized object of type NSPlaceholderString
>   string = NSString.alloc().init()

Python strings get converted to NSStrings automatically where
needed, so is there some reason you can't use an empty Python
string instead?

-- 
Greg

[Pyobjc-dev] memory leak

[Daniel L. d. S. <dan...@gm...>]

Hello,

I have some python code in a pyobjc app. At some point I want to initialize a NSString :

	string = NSString.alloc().init()

In the terminal I get the following output :

/Users/dlsa/code/cirrusstore/client/build/cirrusclient.app/Contents/Resources/menubaractions.py:44: UninitializedDeallocWarning: leaking an uninitialized object of type NSPlaceholderString
  string = NSString.alloc().init()


I have in my objective C bootstrap code the creation of an Auto release pool.

If I try :

	string = NSString.alloc().init().autorelease()

I get the same warning.

Why does this happen ?

Re: [Pyobjc-dev] selector comparision

[Ronald O. <ron...@ma...>]

On 4 May, 2011, at 0:03, Daniel Luis dos Santos wrote:

> Hello, 
> 
> I am following the apple docs on how to enable menu items according to state in my application :
> The doc is at : http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/MenuList/Articles/EnablingMenuItems.html%23//apple_ref/doc/uid/20000261-BAJBFGED
> 
> I am trying to do something similar to the example code of the method 
> 
> 	- (BOOL)validateUserInterfaceItem:(id <NSValidatedUserInterfaceItem>)anItem
> 
> but in python. The class that holds the actions to the menu items has that method implemented as the docs indicate.
> To avoid hardcoding the methodNames in the code I want to compare the result of the action() method to the selector of each method. My code is :
> 
> 	def validateUserInterfaceItem_(self, anItem):
> 		
> 		theAction = anItem.action()
> 		if (theAction == self.saveAction_):
> 			return NO
> 		return YES

I'm not sure if this is worth the effort, you're still duplicating names. The only (small) advantage is that you don't have to use the Objective-C name. A disadvantage of your code is that 'self.saveAction_' creates a bound selector object, which means this code is less efficient that just using the selector name (although the difference is insignificant here).

Anyway, the code above is broken: "theAction" is a selector name (a byte string), while self.saveAction_ is a bound selector object. You should compare to self.saveAction_.selector instead.

> 
> Somewhere in the same class I have the method :
> 
> 	@IBAction
> 	def saveAction_(self, sender):
> 		... rest of method definition
> 
> To have the selector defined for the above method I also put immediately after the method declaration :
> 
> 	saveAction_ = objc.selector(saveAction_, signature="v@:@")

That's not necessary, @IBAction already does this for you.

> 
> The problem is that the comparison of the result of anItem.action() does not equals the selector for the method.
> If I print both to the terminal using :
> 
> 		print theAction
> 		print self.saveAction_
> 
> I get  :
> 
> 		saveAction:
> 		<selector saveAction: of <menubaractions: 0x1010ee000>>
> 
> The output does not match. It seems like the representation is different. How do I compare both these values successfully ?

Your comparing a selector object with a passed in selector name. To compare you should use self.saveAction_.selector,  that attribute contains the selector name.

Ronald

[Pyobjc-dev] selector comparision

[Daniel L. d. S. <dan...@gm...>]

Hello, 

I am following the apple docs on how to enable menu items according to state in my application :
The doc is at : http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/MenuList/Articles/EnablingMenuItems.html%23//apple_ref/doc/uid/20000261-BAJBFGED

I am trying to do something similar to the example code of the method 

	- (BOOL)validateUserInterfaceItem:(id <NSValidatedUserInterfaceItem>)anItem

but in python. The class that holds the actions to the menu items has that method implemented as the docs indicate.
To avoid hardcoding the methodNames in the code I want to compare the result of the action() method to the selector of each method. My code is :

	def validateUserInterfaceItem_(self, anItem):
		
		theAction = anItem.action()
		if (theAction == self.saveAction_):
			return NO
		return YES

Somewhere in the same class I have the method :

	@IBAction
	def saveAction_(self, sender):
		... rest of method definition

To have the selector defined for the above method I also put immediately after the method declaration :

	saveAction_ = objc.selector(saveAction_, signature="v@:@")

The problem is that the comparison of the result of anItem.action() does not equals the selector for the method.
If I print both to the terminal using :

		print theAction
		print self.saveAction_

I get  :

		saveAction:
		<selector saveAction: of <menubaractions: 0x1010ee000>>

The output does not match. It seems like the representation is different. How do I compare both these values successfully ?


Many thanks
Regards

Re: [Pyobjc-dev] header installation issue breaks build for pyobjc 2.3 and 2.4

[Ronald O. <ron...@ma...>]

On 28 Apr, 2011, at 15:07, Zach Pincus wrote:

> [argent:~] zpincus% python -c 'import setuptools; print setuptools.__file__'
> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/setuptools-0.6c11-py2.7.egg/setuptools/__init__.pyc

Thanks. 
> 
> According to pypi where I grabbed the package from, this is the latest
> version... but it does seem to date from late 2009!
> 
> Maybe that's the trouble... sorry for the bother if so!

The setuptools author is even slower than me w.r.t. making new releases :-).    

> 
> Also, for the record, it was a bit tricky to find out how to build the
> packages manually (e.g. start with pyobjc-core and then move to the
> various pyobjc-framework-XXX directories).

Adding documentation for that is on my todo list.   "Easy_install pyobjc" should also work, although I haven't tested that for a while.

Ronald

Re: [Pyobjc-dev] header installation issue breaks build for pyobjc 2.3 and 2.4

[Zach P. <zp...@gm...>]

[argent:~] zpincus% python -c 'import setuptools; print setuptools.__file__'
/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/setuptools-0.6c11-py2.7.egg/setuptools/__init__.pyc

According to pypi where I grabbed the package from, this is the latest
version... but it does seem to date from late 2009!

Maybe that's the trouble... sorry for the bother if so!

Also, for the record, it was a bit tricky to find out how to build the
packages manually (e.g. start with pyobjc-core and then move to the
various pyobjc-framework-XXX directories).

Thanks,
Zach



On Thu, Apr 28, 2011 at 7:26 AM, Ronald Oussoren <ron...@ma...> wrote:
>
> On 27 Apr, 2011, at 18:45, Zach Pincus wrote:
>
>> Hello all,
>>
>> I had some trouble installing from source pyobjc 2.3 or 2.4 from the
>> SVN tag or trunk (respectively), that I seem to have isolated to a
>> problem with pyobjc-core not installing pyobjc-api.h and
>> pyobjc-compat.h into EGG-INFO/include.
>
> That's not good. What version of setuptools/distribute do you use?   The following command should give enough information:
>
> $ python -c 'import setuptools; print setuptools.__file__'
>
> The reason I ask: 'python setup.py install' works on my machine (using a recent version of distribute instead of setuptools).
>
> BTW. I'd like to know the version of setuptools on your machine even if installing distribute fixes the problem for you. There are two reasons for that, firstly I can try to debug why the file doesn't get installed, and secondly I tweak the setup.py of pyobjc-core to give an error message when it detects a too old version of setuptools.
>
> Ronald
>>
>> This causes 'python setup.py install' to fail for other modules.
>>
>> Here's what I did:
>> svn co http://svn.red-bean.com/pyobjc/tags/pyobjc-2.3.1/ pyobjc-2.3.1
>> cd pyobjc-2.3.1/pyobjc-core/
>> python setup.py install
>> cd ../pyobjc-framework-Cocoa
>> python setup.py install
>>>>> FAIL <<<
>>
>> The problem is that, as above, those headers aren't installed into
>> EGG-INFO/include, so they don't show up in the dist info when
>> pyobjc_setup.py requests it, causing that file to instead write out an
>> old and incorrect-for-pyobjc-2.3 api header file (and no compat header
>> file), which then breaks subsequent builds.
>>
>> I fixed this by manually copying the header files to EGG-INFO/include.
>> I did not have time to track down why they weren't installed properly
>> in the first place. I had a similar-looking issue with 2.4 from the
>> trunk, but I did verify that this fix solved it.
>>
>> Perhaps I was going about installing things all wrong, but regardless,
>> I think there's some kind of bug in here. Good luck with that.
>>
>> Zach
>>
>> ------------------------------------------------------------------------------
>> WhatsUp Gold - Download Free Network Management Software
>> The most intuitive, comprehensive, and cost-effective network
>> management toolset available today.  Delivers lowest initial
>> acquisition cost and overall TCO of any competing solution.
>> http://p.sf.net/sfu/whatsupgold-sd
>> _______________________________________________
>> Pyobjc-dev mailing list
>> Pyo...@li...
>> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev
>
>

Re: [Pyobjc-dev] header installation issue breaks build for pyobjc 2.3 and 2.4

[Ronald O. <ron...@ma...>]

On 27 Apr, 2011, at 18:45, Zach Pincus wrote:

> Hello all,
> 
> I had some trouble installing from source pyobjc 2.3 or 2.4 from the
> SVN tag or trunk (respectively), that I seem to have isolated to a
> problem with pyobjc-core not installing pyobjc-api.h and
> pyobjc-compat.h into EGG-INFO/include.

That's not good. What version of setuptools/distribute do you use?   The following command should give enough information:

$ python -c 'import setuptools; print setuptools.__file__'

The reason I ask: 'python setup.py install' works on my machine (using a recent version of distribute instead of setuptools). 

BTW. I'd like to know the version of setuptools on your machine even if installing distribute fixes the problem for you. There are two reasons for that, firstly I can try to debug why the file doesn't get installed, and secondly I tweak the setup.py of pyobjc-core to give an error message when it detects a too old version of setuptools.

Ronald
> 
> This causes 'python setup.py install' to fail for other modules.
> 
> Here's what I did:
> svn co http://svn.red-bean.com/pyobjc/tags/pyobjc-2.3.1/ pyobjc-2.3.1
> cd pyobjc-2.3.1/pyobjc-core/
> python setup.py install
> cd ../pyobjc-framework-Cocoa
> python setup.py install
>>>> FAIL <<<
> 
> The problem is that, as above, those headers aren't installed into
> EGG-INFO/include, so they don't show up in the dist info when
> pyobjc_setup.py requests it, causing that file to instead write out an
> old and incorrect-for-pyobjc-2.3 api header file (and no compat header
> file), which then breaks subsequent builds.
> 
> I fixed this by manually copying the header files to EGG-INFO/include.
> I did not have time to track down why they weren't installed properly
> in the first place. I had a similar-looking issue with 2.4 from the
> trunk, but I did verify that this fix solved it.
> 
> Perhaps I was going about installing things all wrong, but regardless,
> I think there's some kind of bug in here. Good luck with that.
> 
> Zach
> 
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network 
> management toolset available today.  Delivers lowest initial 
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev

[Pyobjc-dev] header installation issue breaks build for pyobjc 2.3 and 2.4

[Zach P. <zp...@gm...>]

Hello all,

I had some trouble installing from source pyobjc 2.3 or 2.4 from the
SVN tag or trunk (respectively), that I seem to have isolated to a
problem with pyobjc-core not installing pyobjc-api.h and
pyobjc-compat.h into EGG-INFO/include.

This causes 'python setup.py install' to fail for other modules.

Here's what I did:
svn co http://svn.red-bean.com/pyobjc/tags/pyobjc-2.3.1/ pyobjc-2.3.1
cd pyobjc-2.3.1/pyobjc-core/
python setup.py install
cd ../pyobjc-framework-Cocoa
python setup.py install
>>> FAIL <<<

The problem is that, as above, those headers aren't installed into
EGG-INFO/include, so they don't show up in the dist info when
pyobjc_setup.py requests it, causing that file to instead write out an
old and incorrect-for-pyobjc-2.3 api header file (and no compat header
file), which then breaks subsequent builds.

I fixed this by manually copying the header files to EGG-INFO/include.
I did not have time to track down why they weren't installed properly
in the first place. I had a similar-looking issue with 2.4 from the
trunk, but I did verify that this fix solved it.

Perhaps I was going about installing things all wrong, but regardless,
I think there's some kind of bug in here. Good luck with that.

Zach

Re: [Pyobjc-dev] mac os x 10.6 installation error

[Greg E. <gre...@ca...>]

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:

http://pypi.python.org/pypi?%3Aaction=search&term=pyobjc&submit=search

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
of this.

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
thing.

-- 
Greg

Re: [Pyobjc-dev] mac os x 10.6 installation error

[David C. <dav...@gm...>]

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-ServiceManagement
pyobjc-framework-ServerNotification
... <snip>...
pyobjc-framework-WebKit
pyobjc-framework-SystemConfiguration (produces a lot of C warnings)
pyobjc-framework-SyncServices
pyobjc-framework-SearchKit
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
correct.

There is something wrong with that install sequence. I'd appreciate
any guidance on how to get around it.

Thanks for your time,

Dave Cortesi

Re: [Pyobjc-dev] mac os x 10.6 installation error

[Div S. <div...@ya...>]

10.6 + Xcode 3 has PyObjC, and I ran the PyGUI demo without any trouble.


~$ python
Python 2.6.1 (r261:67515, Jun 24 2010, 21:47:49) 
[GCC 4.2.1 (Apple Inc. build 5646)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import objc
>>> objc.__version__
'2.2b3'




--- On Fri, 4/15/11, David Cortesi <dav...@gm...> wrote:

> From: David Cortesi <dav...@gm...>
> Subject: [Pyobjc-dev] mac os x 10.6 installation error
> To: pyo...@li...
> Date: Friday, April 15, 2011, 5:44 AM
> Sorry for the newbie question. I'm
> really trying to install PyGUI
> which requires PyObjC. The target is a macbook pro with the
> standard
> Apple python 2.6. I ran easy_install pyobjc; after several
> paragraphs
> of this-n-that it failed for lack of GCC. Oops, I'd never
> installed
> XCode on this machine. I got out the snow leopard dvd and
> installed
> Xcode and reran the easy_install.
> 
> Now it goes almost immediately to compiling a _ScreenSaver_
> module
> which after a number of warnings, fails as follows:
> 
>   lipo: can't open input file:
> /var/folders/Et/EtxW7vM0HTaS6E9e2To88E+++TI/-Tmp-//ccHZxEai.out
> (No
> such file or directory)
>   error: Setup script exited with error: command
> 'gcc-4.2' failed with
> exit status 1
> 
> It may be significant that if you Google 'lipo: can't open
> input file'
> you get many hits related to installing a variety of
> packages such as
> pygame, mysql, etc hence this may be a generic easy_install
> issue with
> Mac 10.6.
> 
> I'll put the whole voluminous record below, feel free to
> snip it in any reply.
> 
> Thanks for any insight,
> 
> Dave Cortesi
> 
> [16:39 ~/Documents/Dprojects/PyGui/pyobjc-2.3] easy_install
> pyobjc
> Searching for pyobjc
> Best match: pyobjc 2.3
> Processing pyobjc-2.3-py2.6.egg
> pyobjc 2.3 is already the active version in
> easy-install.pth
> 
> Using
> /Library/Python/2.6/site-packages/pyobjc-2.3-py2.6.egg
> Processing dependencies for pyobjc
> Searching for pyobjc-framework-ScreenSaver==2.3
> Reading http://pypi.python.org/simple/pyobjc-framework-ScreenSaver/
> Reading http://pyobjc.sourceforge.net
> Best match: pyobjc-framework-ScreenSaver 2.3
> Downloading http://pypi.python.org/packages/source/p/pyobjc-framework-ScreenSaver/pyobjc-framework-ScreenSaver-2.3.tar.gz#md5=f8e9300351df4b8b38e9965b2319562b
> Processing pyobjc-framework-ScreenSaver-2.3.tar.gz
> Running pyobjc-framework-ScreenSaver-2.3/setup.py -q
> bdist_egg
> --dist-dir
> /var/folders/Et/EtxW7vM0HTaS6E9e2To88E+++TI/-Tmp-/easy_install-Hz6ZgM/pyobjc-framework-ScreenSaver-2.3/egg-dist-tmp-a9T9Xs
> /System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/distutils/dist.py:266:
> UserWarning: Unknown distribution option: 'use_2to3'
>   warnings.warn(msg)
> Modules/_ScreenSaver_inlines.m:5: error: expected '=', ',',
> ';', 'asm'
> or '__attribute__' before 'function_map'
> Modules/_ScreenSaver_inlines.m:18: warning: return type
> defaults to 'int'
> Modules/_ScreenSaver_inlines.m:18: warning: function
> declaration isn't
> a prototype
> Modules/_ScreenSaver_inlines.m: In function
> 'PyObjC_MODULE_INIT':
> Modules/_ScreenSaver_inlines.m:19: warning: implicit
> declaration of
> function 'PyObjC_MODULE_CREATE'
> Modules/_ScreenSaver_inlines.m:19: warning: initialization
> makes
> pointer from integer without a cast
> Modules/_ScreenSaver_inlines.m:21: warning: implicit
> declaration of
> function 'PyObjC_INITERROR'
> Modules/_ScreenSaver_inlines.m:25: warning: implicit
> declaration of
> function 'PyObjC_CreateInlineTab'
> Modules/_ScreenSaver_inlines.m:25: error: 'function_map'
> undeclared
> (first use in this function)
> Modules/_ScreenSaver_inlines.m:25: error: (Each undeclared
> identifier
> is reported only once
> Modules/_ScreenSaver_inlines.m:25: error: for each function
> it appears in.)
> Modules/_ScreenSaver_inlines.m:25: warning: passing
> argument 3 of
> 'PyModule_AddObject' makes pointer from integer without a
> cast
> Modules/_ScreenSaver_inlines.m:29: warning: implicit
> declaration of
> function 'PyObjC_INITDONE'
> Modules/_ScreenSaver_inlines.m:5: error: expected '=', ',',
> ';', 'asm'
> or '__attribute__' before 'function_map'
> Modules/_ScreenSaver_inlines.m:18: warning: return type
> defaults to 'int'
> Modules/_ScreenSaver_inlines.m:18: warning: function
> declaration isn't
> a prototype
> Modules/_ScreenSaver_inlines.m: In function
> 'PyObjC_MODULE_INIT':
> Modules/_ScreenSaver_inlines.m:19: warning: implicit
> declaration of
> function 'PyObjC_MODULE_CREATE'
> Modules/_ScreenSaver_inlines.m:19: warning: initialization
> makes
> pointer from integer without a cast
> Modules/_ScreenSaver_inlines.m:21: warning: implicit
> declaration of
> function 'PyObjC_INITERROR'
> Modules/_ScreenSaver_inlines.m:25: warning: implicit
> declaration of
> function 'PyObjC_CreateInlineTab'
> Modules/_ScreenSaver_inlines.m:25: error: 'function_map'
> undeclared
> (first use in this function)
> Modules/_ScreenSaver_inlines.m:25: error: (Each undeclared
> identifier
> is reported only once
> Modules/_ScreenSaver_inlines.m:25: error: for each function
> it appears in.)
> Modules/_ScreenSaver_inlines.m:25: warning: passing
> argument 3 of
> 'PyModule_AddObject' makes pointer from integer without a
> cast
> Modules/_ScreenSaver_inlines.m:29: warning: implicit
> declaration of
> function 'PyObjC_INITDONE'
> Modules/_ScreenSaver_inlines.m:5: error: expected '=', ',',
> ';', 'asm'
> or '__attribute__' before 'function_map'
> Modules/_ScreenSaver_inlines.m:18: warning: return type
> defaults to 'int'
> Modules/_ScreenSaver_inlines.m:18: warning: function
> declaration isn't
> a prototype
> Modules/_ScreenSaver_inlines.m: In function
> 'PyObjC_MODULE_INIT':
> Modules/_ScreenSaver_inlines.m:19: warning: implicit
> declaration of
> function 'PyObjC_MODULE_CREATE'
> Modules/_ScreenSaver_inlines.m:19: warning: initialization
> makes
> pointer from integer without a cast
> Modules/_ScreenSaver_inlines.m:21: warning: implicit
> declaration of
> function 'PyObjC_INITERROR'
> Modules/_ScreenSaver_inlines.m:25: warning: implicit
> declaration of
> function 'PyObjC_CreateInlineTab'
> Modules/_ScreenSaver_inlines.m:25: error: 'function_map'
> undeclared
> (first use in this function)
> Modules/_ScreenSaver_inlines.m:25: error: (Each undeclared
> identifier
> is reported only once
> Modules/_ScreenSaver_inlines.m:25: error: for each function
> it appears in.)
> Modules/_ScreenSaver_inlines.m:25: warning: passing
> argument 3 of
> 'PyModule_AddObject' makes pointer from integer without a
> cast
> Modules/_ScreenSaver_inlines.m:29: warning: implicit
> declaration of
> function 'PyObjC_INITDONE'
> lipo: can't open input file:
> /var/folders/Et/EtxW7vM0HTaS6E9e2To88E+++TI/-Tmp-//ccuckfe1.out
> (No
> such file or directory)
> error: Setup script exited with error: command 'gcc-4.2'
> failed with
> exit status 1
> 
> ------------------------------------------------------------------------------
> Benefiting from Server Virtualization: Beyond Initial
> Workload 
> Consolidation -- Increasing the use of server
> virtualization is a top
> priority.Virtualization can reduce costs, simplify
> management, and improve 
> application availability and disaster protection. Learn
> more about boosting 
> the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev
> 

[Pyobjc-dev] mac os x 10.6 installation error

[David C. <dav...@gm...>]

Sorry for the newbie question. I'm really trying to install PyGUI
which requires PyObjC. The target is a macbook pro with the standard
Apple python 2.6. I ran easy_install pyobjc; after several paragraphs
of this-n-that it failed for lack of GCC. Oops, I'd never installed
XCode on this machine. I got out the snow leopard dvd and installed
Xcode and reran the easy_install.

Now it goes almost immediately to compiling a _ScreenSaver_ module
which after a number of warnings, fails as follows:

  lipo: can't open input file:
/var/folders/Et/EtxW7vM0HTaS6E9e2To88E+++TI/-Tmp-//ccHZxEai.out (No
such file or directory)
  error: Setup script exited with error: command 'gcc-4.2' failed with
exit status 1

It may be significant that if you Google 'lipo: can't open input file'
you get many hits related to installing a variety of packages such as
pygame, mysql, etc hence this may be a generic easy_install issue with
Mac 10.6.

I'll put the whole voluminous record below, feel free to snip it in any reply.

Thanks for any insight,

Dave Cortesi

[16:39 ~/Documents/Dprojects/PyGui/pyobjc-2.3] easy_install pyobjc
Searching for pyobjc
Best match: pyobjc 2.3
Processing pyobjc-2.3-py2.6.egg
pyobjc 2.3 is already the active version in easy-install.pth

Using /Library/Python/2.6/site-packages/pyobjc-2.3-py2.6.egg
Processing dependencies for pyobjc
Searching for pyobjc-framework-ScreenSaver==2.3
Reading http://pypi.python.org/simple/pyobjc-framework-ScreenSaver/
Reading http://pyobjc.sourceforge.net
Best match: pyobjc-framework-ScreenSaver 2.3
Downloading http://pypi.python.org/packages/source/p/pyobjc-framework-ScreenSaver/pyobjc-framework-ScreenSaver-2.3.tar.gz#md5=f8e9300351df4b8b38e9965b2319562b
Processing pyobjc-framework-ScreenSaver-2.3.tar.gz
Running pyobjc-framework-ScreenSaver-2.3/setup.py -q bdist_egg
--dist-dir /var/folders/Et/EtxW7vM0HTaS6E9e2To88E+++TI/-Tmp-/easy_install-Hz6ZgM/pyobjc-framework-ScreenSaver-2.3/egg-dist-tmp-a9T9Xs
/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/distutils/dist.py:266:
UserWarning: Unknown distribution option: 'use_2to3'
  warnings.warn(msg)
Modules/_ScreenSaver_inlines.m:5: error: expected '=', ',', ';', 'asm'
or '__attribute__' before 'function_map'
Modules/_ScreenSaver_inlines.m:18: warning: return type defaults to 'int'
Modules/_ScreenSaver_inlines.m:18: warning: function declaration isn't
a prototype
Modules/_ScreenSaver_inlines.m: In function 'PyObjC_MODULE_INIT':
Modules/_ScreenSaver_inlines.m:19: warning: implicit declaration of
function 'PyObjC_MODULE_CREATE'
Modules/_ScreenSaver_inlines.m:19: warning: initialization makes
pointer from integer without a cast
Modules/_ScreenSaver_inlines.m:21: warning: implicit declaration of
function 'PyObjC_INITERROR'
Modules/_ScreenSaver_inlines.m:25: warning: implicit declaration of
function 'PyObjC_CreateInlineTab'
Modules/_ScreenSaver_inlines.m:25: error: 'function_map' undeclared
(first use in this function)
Modules/_ScreenSaver_inlines.m:25: error: (Each undeclared identifier
is reported only once
Modules/_ScreenSaver_inlines.m:25: error: for each function it appears in.)
Modules/_ScreenSaver_inlines.m:25: warning: passing argument 3 of
'PyModule_AddObject' makes pointer from integer without a cast
Modules/_ScreenSaver_inlines.m:29: warning: implicit declaration of
function 'PyObjC_INITDONE'
Modules/_ScreenSaver_inlines.m:5: error: expected '=', ',', ';', 'asm'
or '__attribute__' before 'function_map'
Modules/_ScreenSaver_inlines.m:18: warning: return type defaults to 'int'
Modules/_ScreenSaver_inlines.m:18: warning: function declaration isn't
a prototype
Modules/_ScreenSaver_inlines.m: In function 'PyObjC_MODULE_INIT':
Modules/_ScreenSaver_inlines.m:19: warning: implicit declaration of
function 'PyObjC_MODULE_CREATE'
Modules/_ScreenSaver_inlines.m:19: warning: initialization makes
pointer from integer without a cast
Modules/_ScreenSaver_inlines.m:21: warning: implicit declaration of
function 'PyObjC_INITERROR'
Modules/_ScreenSaver_inlines.m:25: warning: implicit declaration of
function 'PyObjC_CreateInlineTab'
Modules/_ScreenSaver_inlines.m:25: error: 'function_map' undeclared
(first use in this function)
Modules/_ScreenSaver_inlines.m:25: error: (Each undeclared identifier
is reported only once
Modules/_ScreenSaver_inlines.m:25: error: for each function it appears in.)
Modules/_ScreenSaver_inlines.m:25: warning: passing argument 3 of
'PyModule_AddObject' makes pointer from integer without a cast
Modules/_ScreenSaver_inlines.m:29: warning: implicit declaration of
function 'PyObjC_INITDONE'
Modules/_ScreenSaver_inlines.m:5: error: expected '=', ',', ';', 'asm'
or '__attribute__' before 'function_map'
Modules/_ScreenSaver_inlines.m:18: warning: return type defaults to 'int'
Modules/_ScreenSaver_inlines.m:18: warning: function declaration isn't
a prototype
Modules/_ScreenSaver_inlines.m: In function 'PyObjC_MODULE_INIT':
Modules/_ScreenSaver_inlines.m:19: warning: implicit declaration of
function 'PyObjC_MODULE_CREATE'
Modules/_ScreenSaver_inlines.m:19: warning: initialization makes
pointer from integer without a cast
Modules/_ScreenSaver_inlines.m:21: warning: implicit declaration of
function 'PyObjC_INITERROR'
Modules/_ScreenSaver_inlines.m:25: warning: implicit declaration of
function 'PyObjC_CreateInlineTab'
Modules/_ScreenSaver_inlines.m:25: error: 'function_map' undeclared
(first use in this function)
Modules/_ScreenSaver_inlines.m:25: error: (Each undeclared identifier
is reported only once
Modules/_ScreenSaver_inlines.m:25: error: for each function it appears in.)
Modules/_ScreenSaver_inlines.m:25: warning: passing argument 3 of
'PyModule_AddObject' makes pointer from integer without a cast
Modules/_ScreenSaver_inlines.m:29: warning: implicit declaration of
function 'PyObjC_INITDONE'
lipo: can't open input file:
/var/folders/Et/EtxW7vM0HTaS6E9e2To88E+++TI/-Tmp-//ccuckfe1.out (No
such file or directory)
error: Setup script exited with error: command 'gcc-4.2' failed with
exit status 1

[Pyobjc-dev] ANN: PyGUI 2.4

[Greg E. <gre...@ca...>]

PyGUI 2.4 is available:

   http://www.cosc.canterbury.ac.nz/greg.ewing/python_gui/

Highlights of this release:

* Python 3 Compatible on MacOSX and Windows.

* ScrollableView has been overhauled on Windows and should now
   work with all builds of pywin32 as far as I know.


What is PyGUI?
--------------

PyGUI is a cross-platform GUI toolkit designed to be lightweight
and have a highly Pythonic API.

-- 
Gregory Ewing
gre...@ca...
http://www.cosc.canterbury.ac.nz/greg.ewing/

Re: [Pyobjc-dev] PyObjC won't support Accessibility API

[Ronald O. <ron...@ma...>]

On 17 Mar, 2011, at 0:28, Horky Chen wrote:

> Hi,
> 
> That looks like PyObjC won't support Accessibility APIs, is it right? 
> Accessibility APIs are very useful for UI automation control and checking.

The NSAccessibility informal protocol should work, although I haven't used it myself.

Which other APIs do you want to use? I know PyObjC doesn't yet have 100% API coverage, I'm adding coverage for additional APIs when I find them and have some time to do the work.

Ronald

> 
> Best Regards!
> Horky
> 
> ------------------------------------------------------------------------------
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit
> for your organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev

[Pyobjc-dev] PyObjC won't support Accessibility API

[Horky C. <scu...@gm...>]

Hi,

That looks like PyObjC won't support Accessibility APIs, is it right? 
Accessibility APIs are very useful for UI automation control and checking.

Best Regards!
Horky

Re: [Pyobjc-dev] XCode 4.0

[Ronald O. <ron...@ma...>]

On 15 Mar, 2011, at 14:13, Nicholas Cole wrote:

> Dear List,
> 
> Has anyone had any luck installing templates and using PyObjC with XCode 4?

I guess I should have posted the message here as well (I only posted to pythonmac-sig):  Xcode4 sucks w.r..t support for scripting languages. I haven't tried using the pyobjc xcode templates yet, but at the very least the new embedded version of Interface Builder doesn't support PyObjC  (or any other scripting language).

I've filed a bug at Apple, and I advise anyone that uses PyObjC to write GUI code to do the same.

Ronald

> 
> Best wishes,
> 
> Nicholas
> 
> ------------------------------------------------------------------------------
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit
> for your organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev

[Pyobjc-dev] XCode 4.0

[Nicholas C. <nic...@gm...>]

Dear List,

Has anyone had any luck installing templates and using PyObjC with XCode 4?

Best wishes,

Nicholas

Re: [Pyobjc-dev] CTFontManager*

[Ronald O. <ron...@ma...>]

On 2 Mar, 2011, at 16:10, Tal Leming wrote:

> Hello,
> 
> I'm trying to use several CTFontManager functions via PyObjC but it looks like the framework isn't fully wrapped:
> 
>>>> from CoreText import CTFontManagerRegisterFontsForURL
> Traceback (most recent call last):
>  File "<stdin>", line 1, in <module>
> ImportError: cannot import name CTFontManagerRegisterFontsForURL
> 
> (This was with the OS Python in 10.6.)
> 
> Is there a way to get to these functions with Python?

You'll have to load this function manually for now, and  I'll try to add it to the bridgesupport files for the next release.

Ronald
> 
> Tal
> ------------------------------------------------------------------------------
> Free Software Download: Index, Search & Analyze Logs and other IT data in 
> Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
> generated by your applications, servers and devices whether physical, virtual
> or in the cloud. Deliver compliance at lower cost and gain new business 
> insights. http://p.sf.net/sfu/splunk-dev2dev 
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev

[Pyobjc-dev] CTFontManager*

[Tal L. <ta...@ty...>]

Hello,

I'm trying to use several CTFontManager functions via PyObjC but it looks like the framework isn't fully wrapped:

>>> from CoreText import CTFontManagerRegisterFontsForURL
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: cannot import name CTFontManagerRegisterFontsForURL

(This was with the OS Python in 10.6.)

Is there a way to get to these functions with Python?

Tal

[Pyobjc-dev] [ pyobjc-Bugs-3195876 ] pip install pyobjc fails

[SourceForge.net <no...@so...>]

Bugs item #3195876, was opened at 2011-02-28 23:44
Message generated for change (Tracker Item Submitted) made by 
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=114534&aid=3195876&group_id=14534

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Leif Johnson ()
Assigned to: Nobody/Anonymous (nobody)
Summary: pip install pyobjc fails

Initial Comment:
I have installed a new version of Python (2.7) on my Mac using brew, and successfully installed a number of packages thereafter using pip. I am trying to get matplotlib up and running, and it needs PyObjC for the rendering backend. However, when I try "pip install pyobjc" it fails with a traceback when trying to install pyobjc-core :

Downloading/unpacking pyobjc-core==2.3 (from PyObjC)
  Running setup.py egg_info for package pyobjc-core
    Traceback (most recent call last):
      File "<string>", line 14, in <module>
      File "/usr/local/var/pip/build/pyobjc-core/setup.py", line 452, in <module>
        **extra_args
      File "/usr/local/Cellar/python/2.7.1/lib/python2.7/distutils/core.py", line 152, in setup
        dist.run_commands()
      File "/usr/local/Cellar/python/2.7.1/lib/python2.7/distutils/dist.py", line 953, in run_commands
        self.run_command(cmd)
      File "/usr/local/Cellar/python/2.7.1/lib/python2.7/distutils/dist.py", line 972, in run_command
        cmd_obj.run()
      File "/usr/local/var/pip/build/pyobjc-core/setup.py", line 110, in run
        orig_egg_info.egg_info.run(self)
      File "<string>", line 7, in replacement_run
    AttributeError: class egg_info has no attribute 'iter_entry_points'

I've tried peeking at the setup.py file in pyobjc-core, and it seems to do some confusing things like importing a module and using it as a superclass (?). At any rate, frustrating. Any help on this would be much appreciated ! I'm happy to provide more info, too, if it helps pin down what's going on here.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=114534&aid=3195876&group_id=14534

Re: [Pyobjc-dev] Pyobjc creating multiple instances instead of one?!

[Div S. <div...@ya...>]

Doh!  Was stuck on this for 2 days, and figured it out 5 mins after I sent the email.

Forgot to do the correct init stuff:

        self = super(currconvpyAppDelegate, self).init()
        ...
        return self

which is the python equivalent of the objective-c:

    if (self = [super init]) {
        ...
    }
    return self;

Sorry - at least hope this helps other people who get stuck. :)

[Pyobjc-dev] Pyobjc creating multiple instances instead of one?!

[Div S. <div...@ya...>]

pyobjc seems to be creating multiple instances for what should be a single instance.
To recreate: follow the cocoa tutorial (currency converter) and put NSLog statements in the init() for the app delegate and the controller classes.
With objective-c, the output is:    Controller init    AppDelegate init
With pyobjc, the output is:    Controller init    AppDelegate init    AppDelegate init    Controller init    Controller init    Controller init    Controller init
(with different values of 'self')
What's going on here?!
I'm using Xcode 3.2.3 on OS X 10.6.