pyobjc-dev — CVS commit notices go here

[Pyobjc-dev] CoreData problem

[Mark W. <ma...@ta...>]

I have the following code in both Objective-C (compiled as Cocoa tool) and Python as below, with the same input arguments both run to completion without error however the ObjectiveC version creates the sqlite3 db file and the python version doesn't. I'm stuck as to why and was planning on using python in this way to populate database for shipping in app bundle. Anyone got any clues?

Thanks
Mark

#import <Foundation/Foundation.h>
#import <CoreData/CoreData.h>

int main(int argc, char *argv[])
{
    printf("Using Managed Object Models from %s\n", argv[1]);
    printf("Creating sqlite database %s\n", argv[2]);
    
    NSError *err = Nil;

    NSAutoreleasePool *pool = [ [ NSAutoreleasePool alloc ] init ];
    
    // Load model
    NSBundle *bundle = [ NSBundle bundleWithPath:[ NSString stringWithCString:argv[1] encoding:NSUTF8StringEncoding ] ];
    NSArray *bundleArray = [ NSArray arrayWithObject:bundle ];
    NSManagedObjectModel *mom = [ NSManagedObjectModel mergedModelFromBundles:bundleArray ];
    if (!mom)
    {
        NSLog(@"Unable to load model");
        return 1;
    }
        
    // Setup persistent store
    NSURL *urlForDb = [ NSURL fileURLWithPath:[ NSString stringWithCString:argv[2] encoding:NSUTF8StringEncoding ] ];
    NSPersistentStoreCoordinator *psc = [ [ NSPersistentStoreCoordinator alloc ] initWithManagedObjectModel:mom ];
    NSPersistentStore *ps = [ psc addPersistentStoreWithType:NSSQLiteStoreType configuration:Nil URL:urlForDb options:Nil error:&err ];
    
    if (!ps)
    {
        NSLog(@"%@", err.description);
        return 1;
    }
            
    [ pool release ];
    
    return 0;
}

and...

#!/usr/bin/python2.6

from CoreData import *
from Foundation import *
import sys
        
if __name__ == '__main__':

    print 'Using Managed Object Models from', sys.argv[1]
    print 'Creating sqlite database', sys.argv[2]

    err = None
    
    pool = NSAutoreleasePool.alloc().init()
    
    # Load model
    bundle = NSBundle.bundleWithPath_(sys.argv[1])
    bundleArray = NSArray.arrayWithObject_(bundle)
    mom = NSManagedObjectModel.mergedModelFromBundles_(bundleArray)
    if mom is None:
        raise "Unable to load model"
        
    # Setup persistent store
    urlForDb = NSURL.fileURLWithPath_(sys.argv[2])
    psc = NSPersistentStoreCoordinator.alloc().initWithManagedObjectModel_(mom)
    ps = psc.addPersistentStoreWithType_configuration_URL_options_error_(NSSQLiteStoreType, None, urlForDb, None, err)
    if ps is None:
        raise err.description()

    pool.release()

[Pyobjc-dev] [ pyobjc-Bugs-2927630 ] Growl Framework Does Not Work With PyObjc 2.2b3

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

Bugs item #2927630, was opened at 2010-01-07 15:59
Message generated for change (Tracker Item Submitted) made by 
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=114534&aid=2927630&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: https://www.google.com/accounts ()
Assigned to: Nobody/Anonymous (nobody)
Summary: Growl Framework Does Not Work With PyObjc 2.2b3

Initial Comment:
The problem is outlined with a test case here: http://groups.google.com/group/growldiscuss/browse_thread/thread/ccd8601313ac13ec

An application can register to growl fine but posting notifications does not work using the following code:

GrowlApplicationBridge.notifyWithTitle_description_notificationName_iconData_priority_isSticky_clickContext_(u"Notification", "A description.", u"Notification", objc.nil, 0, objc.NO, objc.nil)

But it does work with the following code:

GrowlApplicationBridge.notifyWithTitle_description_notificationName_iconData_priority_isSticky_clickContext_(NSString.stringWithString_("Notification"), NSString.stringWithString_("A description."), NSString.stringWithString_("Notification"), objc.nil, 0, objc.NO, objc.nil)

For some reason it looks it requires a 'real' NSString to be passed through the bridge (not a OC_PythonString)

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

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

Re: [Pyobjc-dev] Fwd: PyObjC and NSOpenGLView

[Tobias W. <t.w...@im...>]

On 5 Jan 2010, at 10:43, Ronald Oussoren wrote:

> 
> Sorry about not replying sooner. "py2app -A" doesn't work at the moment on SL, IIRC someone has sent me a fix for that.
> 
> You should be able to run the example using 'python setup.py py2app' without the -A.
> 
> Ronald, who's too lazy to run the example himself ;-)

Thanks Ronald, I seem to have things working now. I ran py2app without -A, and then had to correct a couple of other problems with the OpenGL demo -
1) py2app was not copying ctypes.utils into Resources/ properly, this is used somewhere deep in PyOpenGL. Fixed by importing in OpenGLDemo.py so py2app picks it up (Ugly but works)
2) The call to glViewport needs a cast to int for the width and height of the view rect, which are passed in as floats.
I've attached my modified OpenGLDemo.py below. I then used this as the basis for my WorldView class, and it seems to be working including the call to gluPerspective. I'll let you know if I have any more trouble.

Thanks for the help, it is much appreciated.

Toby
 

Re: [Pyobjc-dev] Fwd: PyObjC and NSOpenGLView

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

On 5 Jan, 2010, at 0:46, Tobias Wood wrote:

> Sorry for the forwarded message below, have just realised I responded to Ronald only and failed to cc the list. Has anyone else successfully run the OpenGL example on Snow Leopard?

Sorry about not replying sooner. "py2app -A" doesn't work at the moment on SL, IIRC someone has sent me a fix for that.

You should be able to run the example using 'python setup.py py2app' without the -A.

Ronald, who's too lazy to run the example himself ;-)

> 
> Toby
> 
> Begin forwarded message:
> 
>> From: Tobias Wood <tw...@im...>
>> Date: 3 January 2010 20:00:48 GMT
>> To: Ronald Oussoren <ron...@ma...>
>> Subject: Re: [Pyobjc-dev] PyObjC and NSOpenGLView
>> 
>> Thanks for the prompt reply.
>> 
>> On 3 Jan 2010, at 17:26, Ronald Oussoren wrote:
>>> 
>>> I don't use NSOpenGLView myself, maybe someone else knows the answer.   Does the OpenGL example work for you? <http://pyobjc.sourceforge.net/examples/pyobjc-framework-Cocoa/OpenGL/OpenGLDemo/index.html>
>>> 
>> 
>> Unfortunately not. After doing "python setup.py py2app -A" from within the demo directory, running the resulting app in /dist fails with:
>> 
>> 03/01/2010 19:51:40	[0x0-0x53053].org.pythonmac.unspecified.OpenGLDemo[539]	  File "/Users/Tobias/Downloads/PyObjCExample-OpenGLDemo/dist/OpenGLDemo.app/Contents/Resources/__boot__.py", line 46, in _run
>> 03/01/2010 19:51:40	[0x0-0x53053].org.pythonmac.unspecified.OpenGLDemo[539]	    target, wasChanged = alias.ResolveAlias(None)
>> 03/01/2010 19:51:40	[0x0-0x53053].org.pythonmac.unspecified.OpenGLDemo[539]	AttributeError: 'Carbon.File.Alias' object has no attribute 'ResolveAlias'
>> 03/01/2010 19:51:41	OpenGLDemo[539]	OpenGLDemo Error
>> 03/01/2010 19:51:41	OpenGLDemo[539]	OpenGLDemo Error
>> An unexpected error has occurred during execution of the main script
>> 
>> AttributeError: 'Carbon.File.Alias' object has no attribute 'ResolveAlias'
>> 03/01/2010 19:51:47	com.apple.launchd.peruser.501[89]	([0x0-0x53053].org.pythonmac.unspecified.OpenGLDemo[539]) Exited with exit code: 255
>> 
>> Apologies, I should have mentioned that I'm running Snow Leopard (Which I think will be why Carbon fails) using the system Python (2.6).
>> 
>> Toby
> 
> 
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev 
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev

[Pyobjc-dev] Fwd: PyObjC and NSOpenGLView

[Tobias W. <t.w...@im...>]

Sorry for the forwarded message below, have just realised I responded to Ronald only and failed to cc the list. Has anyone else successfully run the OpenGL example on Snow Leopard?

Toby

Begin forwarded message:

> From: Tobias Wood <tw...@im...>
> Date: 3 January 2010 20:00:48 GMT
> To: Ronald Oussoren <ron...@ma...>
> Subject: Re: [Pyobjc-dev] PyObjC and NSOpenGLView
> 
> Thanks for the prompt reply.
> 
> On 3 Jan 2010, at 17:26, Ronald Oussoren wrote:
>> 
>> I don't use NSOpenGLView myself, maybe someone else knows the answer.   Does the OpenGL example work for you? <http://pyobjc.sourceforge.net/examples/pyobjc-framework-Cocoa/OpenGL/OpenGLDemo/index.html>
>> 
> 
> Unfortunately not. After doing "python setup.py py2app -A" from within the demo directory, running the resulting app in /dist fails with:
> 
> 03/01/2010 19:51:40	[0x0-0x53053].org.pythonmac.unspecified.OpenGLDemo[539]	  File "/Users/Tobias/Downloads/PyObjCExample-OpenGLDemo/dist/OpenGLDemo.app/Contents/Resources/__boot__.py", line 46, in _run
> 03/01/2010 19:51:40	[0x0-0x53053].org.pythonmac.unspecified.OpenGLDemo[539]	    target, wasChanged = alias.ResolveAlias(None)
> 03/01/2010 19:51:40	[0x0-0x53053].org.pythonmac.unspecified.OpenGLDemo[539]	AttributeError: 'Carbon.File.Alias' object has no attribute 'ResolveAlias'
> 03/01/2010 19:51:41	OpenGLDemo[539]	OpenGLDemo Error
> 03/01/2010 19:51:41	OpenGLDemo[539]	OpenGLDemo Error
> An unexpected error has occurred during execution of the main script
> 
> AttributeError: 'Carbon.File.Alias' object has no attribute 'ResolveAlias'
> 03/01/2010 19:51:47	com.apple.launchd.peruser.501[89]	([0x0-0x53053].org.pythonmac.unspecified.OpenGLDemo[539]) Exited with exit code: 255
> 
> Apologies, I should have mentioned that I'm running Snow Leopard (Which I think will be why Carbon fails) using the system Python (2.6).
> 
> Toby

Re: [Pyobjc-dev] PyObjC and NSOpenGLView

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

On 3 Jan, 2010, at 16:46, Tobias Wood wrote:

> Hello,
> First off, sorry if this is the wrong place to post this - I couldn't find a PyObjC users list. If there's a better place to post please let me know and I'll send it there.

This list is fine, an other list where PyObjC and other mac users hang out is the pythonmac-sig list.

> 
> I've been trying to rewrite a game of mine using PyObjC - it's currently a horrible mess of Objective-C and C++ and I think PyObjC will be a much better infrastructure. Unfortunately I'm failing at the first hurdle - implementing a subclass of NSOpenGLView working by reimplementing my Objective-C version line-by-line in PyObjC. I've got two problems with it:
> 1) The NSOpenGLView seems to interfere with the drawing of the Window it's in. When I don't have the NSOpenGLView instantiated in Interface Builder, I'll get the standard grey/silver background in the window. Once I add the NSOpenGLView, the Window is suddenly filled in white (The OpenGLView is drawn correctly on top).
> 2) If I try to use the GLU function gluPerspective I get the following unexpected error (My subclass is called WorldView, code is at the end of this message):
> ValueError: NSInvalidArgumentException - Unlocking Focus on wrong view (<NSThemeFrame:0x2c11580>), expected <WorldView: 0x4e7850>)
> Should I not be subclassing NSOpenGLView? Should I be subclassing something else? I've included my current sub-class below.

I don't use NSOpenGLView myself, maybe someone else knows the answer.   Does the OpenGL example work for you? <http://pyobjc.sourceforge.net/examples/pyobjc-framework-Cocoa/OpenGL/OpenGLDemo/index.html>

> 
> On a different note, when I started this project I was intending to write the interface mainly in Objective-C and the game engine in Python. However the PyObjC examples all seem to be geared towards writing everything in Python. Is there a recommended way to call Python-implemented objects from Objective-C code? The only way I could find to do it is something along the lines of:
> 
> id someObject;
> Class PythonClass = NSClassFromString(@"PythonName");
> someObject = [PythonClass new];
> 
> but I was wondering if there was any other way?

That's basicly the best way, you could also add an Objective-C class where the Python code can register objects or classes.

Ronald

Re: [Pyobjc-dev] Warning: PyObjC repository will be unstable for a while

[Orestis M. <or...@or...>]

On 2 Jan 2010, at 19:38, Ronald Oussoren wrote:

> 
> On 2 Jan, 2010, at 16:54, Orestis Markou wrote:
> 
>> On 2 Jan 2010, at 14:35, Ronald Oussoren wrote:
>> 
>>> The code in the PyObjC repository will be unstable for a while due to some updates I'm working on. In particular, my next commit to pyobjc-core will break most  framework wrappers. That will be fixed in due time, but until then it would be better to not compile from the repository.
>>> 
>>> 
>>> The update I'm working on is a port to Python 3.x, which is progressing nicely although slower than I'd like. I'm currently at a point where I'm reasonably sure that nothing is horribly broken, although the port is not finished yet.   
>> 
>> Wouldn't it be simpler if this happened on a branch? Unless somehow it's compatible with both 2.x and 3.x at the same time (which can be hard if not impossible, from what I can gather).
> 
> The C code is compatible with both versions and the python code is translated using 2to3.  Working on a branch is not simpler for me because branches in svn suck, even if they suck less than branches in CVS.    At this time branches are just overhead for me and hence a way to further slow down development.
> 
> Ronald

Fair enough. 

Orestis

>>> The framework wrappers are not yet avaiable on Python 3.x, making that port unusable for normal use. I will port those once I'm happy about the port of pyobjc-core, that should be a lot less work than porting the brige itself.
>>> 
>>> BTW. I'm also slowly moving the pyobjc documentation to sphinx, the toolchain used to build the Python documentation.
>> 
>> Excellent news! Many thanks for your work, and a happy new year!
>> 
>>> Ronald
>>> 
>>> ------------------------------------------------------------------------------
>>> This SF.Net email is sponsored by the Verizon Developer Community
>>> Take advantage of Verizon's best-in-class app development support
>>> A streamlined, 14 day to market process makes app distribution fast and easy
>>> Join now and get one step closer to millions of Verizon customers
>>> http://p.sf.net/sfu/verizon-dev2dev _______________________________________________
>>> Pyobjc-dev mailing list
>>> Pyo...@li...
>>> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev
>> 
> 

[Pyobjc-dev] PyObjC and NSOpenGLView

[Tobias W. <t.w...@im...>]

Hello,
First off, sorry if this is the wrong place to post this - I couldn't find a PyObjC users list. If there's a better place to post please let me know and I'll send it there.

I've been trying to rewrite a game of mine using PyObjC - it's currently a horrible mess of Objective-C and C++ and I think PyObjC will be a much better infrastructure. Unfortunately I'm failing at the first hurdle - implementing a subclass of NSOpenGLView working by reimplementing my Objective-C version line-by-line in PyObjC. I've got two problems with it:
1) The NSOpenGLView seems to interfere with the drawing of the Window it's in. When I don't have the NSOpenGLView instantiated in Interface Builder, I'll get the standard grey/silver background in the window. Once I add the NSOpenGLView, the Window is suddenly filled in white (The OpenGLView is drawn correctly on top).
2) If I try to use the GLU function gluPerspective I get the following unexpected error (My subclass is called WorldView, code is at the end of this message):
ValueError: NSInvalidArgumentException - Unlocking Focus on wrong view (<NSThemeFrame:0x2c11580>), expected <WorldView: 0x4e7850>)
Should I not be subclassing NSOpenGLView? Should I be subclassing something else? I've included my current sub-class below.

On a different note, when I started this project I was intending to write the interface mainly in Objective-C and the game engine in Python. However the PyObjC examples all seem to be geared towards writing everything in Python. Is there a recommended way to call Python-implemented objects from Objective-C code? The only way I could find to do it is something along the lines of:

id someObject;
Class PythonClass = NSClassFromString(@"PythonName");
someObject = [PythonClass new];

but I was wondering if there was any other way?

Thanks in advance for any help,
Toby Wood

WorldView.py:

from objc import YES, NO, IBAction, IBOutlet
from Foundation import *
from AppKit import *
from OpenGL.GL import *
from OpenGL.GLU import *

class WorldView(NSOpenGLView):
   def awakeFromNib(self):
       NSLog(u'Awoke')

   def initWithFrame_(self, frame):
       self = super(WorldView, self).initWithFrame_(frame)
       if self:
           # initialization code here
           pass
       NSLog(u'init')
       return self

   def prepareOpenGL(self):
       NSLog(u'Prep')
       glClearColor(1.0,0.0,0.0,1.0)

   def reshape(self):
       NSLog(u'Reshape')
       rect = self.bounds()
       glViewport(0, 0, int(rect.size.width), int(rect.size.height))

       if (rect.size.height == 0.0):
           rect.size.height == 1.0

       aspect = rect.size.width/rect.size.height
       glMatrixMode(GL_PROJECTION)
       glLoadIdentity()
       gluPerspective(45.0, fAspect, 1., 1000.)    # Fails on this line
       glMatrixMode(GL_MODELVIEW)
       glLoadIdentity()

   def drawRect_(self, rect):
       # drawing code here
       NSLog(u'Drawing')
       glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT)
       glFlush()

[Pyobjc-dev] [ pyobjc-Bugs-2925086 ] Return Value Mismatch

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

Bugs item #2925086, was opened at 2010-01-03 01:28
Message generated for change (Tracker Item Submitted) made by 
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=114534&aid=2925086&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: https://www.google.com/accounts ()
Assigned to: Nobody/Anonymous (nobody)
Summary: Return Value Mismatch

Initial Comment:
I'm having a problem with NSTableView's delegate method tableView_toolTipForCell_rect_tableColumn_row_mouseLocation_. When this method is called from the table view and the correct value is returned (a string) the following error occurs (attached project reproduces this problem):

TypeError: tableView:toolTipForCell:rect:tableColumn:row:mouseLocation:: Need tuple of 2 arguments as result

I'm running snow leopard with the default pyobjc installation.

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

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

Re: [Pyobjc-dev] Warning: PyObjC repository will be unstable for a while

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

On 2 Jan, 2010, at 16:54, Orestis Markou wrote:

> On 2 Jan 2010, at 14:35, Ronald Oussoren wrote:
> 
>> The code in the PyObjC repository will be unstable for a while due to some updates I'm working on. In particular, my next commit to pyobjc-core will break most  framework wrappers. That will be fixed in due time, but until then it would be better to not compile from the repository.
>> 
>> 
>> The update I'm working on is a port to Python 3.x, which is progressing nicely although slower than I'd like. I'm currently at a point where I'm reasonably sure that nothing is horribly broken, although the port is not finished yet.   
> 
> Wouldn't it be simpler if this happened on a branch? Unless somehow it's compatible with both 2.x and 3.x at the same time (which can be hard if not impossible, from what I can gather).

The C code is compatible with both versions and the python code is translated using 2to3.  Working on a branch is not simpler for me because branches in svn suck, even if they suck less than branches in CVS.    At this time branches are just overhead for me and hence a way to further slow down development.

Ronald

> 
>> The framework wrappers are not yet avaiable on Python 3.x, making that port unusable for normal use. I will port those once I'm happy about the port of pyobjc-core, that should be a lot less work than porting the brige itself.
>> 
>> BTW. I'm also slowly moving the pyobjc documentation to sphinx, the toolchain used to build the Python documentation.
> 
> Excellent news! Many thanks for your work, and a happy new year!
> 
>> Ronald
>> 
>> ------------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Verizon Developer Community
>> Take advantage of Verizon's best-in-class app development support
>> A streamlined, 14 day to market process makes app distribution fast and easy
>> Join now and get one step closer to millions of Verizon customers
>> http://p.sf.net/sfu/verizon-dev2dev _______________________________________________
>> Pyobjc-dev mailing list
>> Pyo...@li...
>> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev
> 

Re: [Pyobjc-dev] Warning: PyObjC repository will be unstable for a while

[Orestis M. <or...@or...>]

On 2 Jan 2010, at 14:35, Ronald Oussoren wrote:

> The code in the PyObjC repository will be unstable for a while due to some updates I'm working on. In particular, my next commit to pyobjc-core will break most  framework wrappers. That will be fixed in due time, but until then it would be better to not compile from the repository.
> 
> 
> The update I'm working on is a port to Python 3.x, which is progressing nicely although slower than I'd like. I'm currently at a point where I'm reasonably sure that nothing is horribly broken, although the port is not finished yet.   

Wouldn't it be simpler if this happened on a branch? Unless somehow it's compatible with both 2.x and 3.x at the same time (which can be hard if not impossible, from what I can gather).

> The framework wrappers are not yet avaiable on Python 3.x, making that port unusable for normal use. I will port those once I'm happy about the port of pyobjc-core, that should be a lot less work than porting the brige itself.
> 
> BTW. I'm also slowly moving the pyobjc documentation to sphinx, the toolchain used to build the Python documentation.

Excellent news! Many thanks for your work, and a happy new year!

> Ronald
> 
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev

[Pyobjc-dev] Warning: PyObjC repository will be unstable for a while

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

The code in the PyObjC repository will be unstable for a while due to some updates I'm working on. In particular, my next commit to pyobjc-core will break most  framework wrappers. That will be fixed in due time, but until then it would be better to not compile from the repository.


The update I'm working on is a port to Python 3.x, which is progressing nicely although slower than I'd like. I'm currently at a point where I'm reasonably sure that nothing is horribly broken, although the port is not finished yet.   

The framework wrappers are not yet avaiable on Python 3.x, making that port unusable for normal use. I will port those once I'm happy about the port of pyobjc-core, that should be a lot less work than porting the brige itself.

BTW. I'm also slowly moving the pyobjc documentation to sphinx, the toolchain used to build the Python documentation.

Ronald

Re: [Pyobjc-dev] Strange PyObjC behavior

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

On 16 Dec, 2009, at 11:14, Artem Y wrote:
> 
> How could all this happen if OS X versions and objc.__version__ are the same ?

That's odd, the change in behaviour seems to indicate that the various machines do not use the same version of PyObjC.
> 
> My program released under GPL and is quite simple, I'd appreciate if someone could test it out and see what's wrong.

Where can I download it?

Ronald

[Pyobjc-dev] Strange PyObjC behavior

[Artem Y <ya...@ym...>]

Hi All,

I'm writing simple PyObjC application and I faced strange problem. I do development on 10.6 using Xcode (10.5 Base SDK) and also test it on my other 10.5 Mac. Everything works well on my machines, but some users complains, for example, I was using NSFormatters, this formatter worked fine on both of my machines:

class MyFormatter(NSFormatter):
    def stringForObjectValue_(self, val):
        return str(val)

    def getObjectValue_forString_errorDescription_(self, v):
        return (True, formatingFunction(v), None)

but I received complains from users, their crash report said "class MyFormatter(NSFormatter): objc.BadPrototypeError: Objective-C expects 4 arguments, Python argument has 2 arguments for ", but they were using 10.6.2 and their objc.__version__ was '2.2b3', same as on my 10.6 machine. It's obvious that "getObjectValue_forString_errorDescription_" should take 4 arguments(including self) but it didn't work with 4 arguments on my machine. I just get rid of NSFormatters to solve this issue.

The other thing, I needed to add Growl support, I created this wrapper:

class GrowlWrapper(NSObject):
    
    def init(self, name):
        self = super(GrowlWrapper, self).init()
        self.name = name
        objc.loadBundle("GrowlApplicationBridge", globals(),
                         bundle_path=objc.pathForFramework(os.path.dirname(sys.argv[0]) + '/../Frameworks/Growl.framework'))

        self._growl = GrowlApplicationBridge
        self._growl.setGrowlDelegate_(self)
        return self
        
    def notify(self, title, description):
        self._growl.notifyWithTitle_description_notificationName_iconData_priority_isSticky_clickContext_(title, 
                                                                                                          description, self.name,None,
                                                                                                          0,False,NSDate.date())

As usual everything was ok on my machines, but other users had problems, their crash report complained that GrowlWrapper.init takes 2 arguments instead of 1. I deleted additional argument   - program didn't crash and worked fine except that it didn't show Growl popup, no messages on Console, however on my machines new GrowlWrapper worked fine. And right now I don't have any clue how to fix it.

How could all this happen if OS X versions and objc.__version__ are the same ?

My program released under GPL and is quite simple, I'd appreciate if someone could test it out and see what's wrong.

Many thanks,
Artem


      

Re: [Pyobjc-dev] Extending Cocoa application

[Vladimir P. <far...@gm...>]

Never mind, that was a typo on my side, everything is working perfectly.

On Sun, Dec 13, 2009 at 19:33, Vladimir Pouzanov <far...@gm...> wrote:
> Hi all,
>
> I have a problem with extending a Cocoa application. I've added
> Python.framework and checked that the target application is linked
> with it, however gcc fails to find both headers and library:

-- 
Sincerely,
Vladimir "Farcaller" Pouzanov
http://farcaller.net/

[Pyobjc-dev] Extending Cocoa application

[Vladimir P. <far...@gm...>]

Hi all,

I have a problem with extending a Cocoa application. I've added
Python.framework and checked that the target application is linked
with it, however gcc fails to find both headers and library:

Ld build/Debug/Transmission.app/Contents/MacOS/Transmission normal x86_64
cd /Users/farcaller/Development/Hacks/Transmission
setenv MACOSX_DEPLOYMENT_TARGET 10.5
/Developer/usr/bin/gcc-4.2 -arch x86_64 -isysroot
/Developer/SDKs/MacOSX10.6.sdk
-L/Users/farcaller/Development/Hacks/Transmission/build/Debug
-Lthird-party/curl/lib -Lthird-party/openssl/lib
-F/Users/farcaller/Development/Hacks/Transmission/build/Debug -Fmacosx
-filelist /Users/farcaller/Development/Hacks/Transmission/build/Transmission.build/Debug/Transmission.build/Objects-normal/x86_64/Transmission.LinkFileList
-mmacosx-version-min=10.5 -framework Cocoa -framework IOKit
-ltransmission -lcrypto.0.9.7 -framework Sparkle -framework Growl
-lcurl.4 -framework Security -framework Carbon -framework Quartz
-framework Python -o
/Users/farcaller/Development/Hacks/Transmission/build/Debug/Transmission.app/Contents/MacOS/Transmission

Undefined symbols:
  "_PyInitialize", referenced from:
      -[PythonController init] in PythonController.o
  "_PyFinalize", referenced from:
      -[PythonController dealloc] in PythonController.o
ld: symbol(s) not found
collect2: ld returned 1 exit status

Any hints for this one?

Also, can someone point me to any example of exposing ObjC class
instance to python code?

-- 
Sincerely,
Vladimir "Farcaller" Pouzanov
http://farcaller.net/

Re: [Pyobjc-dev] PyObjC 2.2 and MachSignals

[Jonathan S. <jon...@ga...>]

Hello,
Can someone tell me something about this? ;-)

~jonathan

On Mon, Nov 30, 2009 at 1:47 AM, Jonathan Stoppani
<jon...@ga...> wrote:
> Hi All,
> my first post here. ;-)
>
> I'm trying to use the twisted networking library integrating some
> QTKit functionalities into the application.
>
> I run my console script interleaving twisted's reactor with
> AppHelper.callLater and all works fine, except for the shutdown after
> a SIGINT.
>
> After digging into the code I found that the installInterrupt=True
> parameter of AppHelper.runConsoleEventLoop() imports from
> PyObjCTools/MachSignals.py which uses the _machsignals module.
>
> I tried a search in google and finally found a reference to a
> machsignals.m file which creates a _machsignal python module in PyObjC
> version 1.3.
>
> Searching the 2.2 codebase I found a reference to this file in
> pyobjc/pyobjc-core/MANIFEST (line 771):
> Modules/CoreFoundation/machsignals.m but the file (and the folder)
> does not exists.
>
> Is this incoherence a bug or is there another way to trigger the
> SIGINT handling code from python while not running python code?
>
> Thanks for the help, greets
>
> ~jonathan
>
> P.S. Hitting C-c on the command line produces the following error:
>
> ^C2009-11-30 01:14:38.203 python[82197:10b] *** NSRunLoop ignoring
> exception '<type 'exceptions.KeyboardInterrupt'>: ' that raised during
> posting of delayed perform with target 0x3181cb0 and selector
> 'callAfter:'
>
>
> --
> Best Regards,
> Jonathan Stoppani
>



-- 
Best Regards,
Jonathan Stoppani

[Pyobjc-dev] ValueError ONLY when using py2app, not otherwise

[Ratko J. <rja...@gm...>]

Hello,

I have run into a bit of a problem with running my app after packaging it
with py2app on Snow Leopard:

*File "build/bdist.macosx-10.3-fat/egg/Quartz/__init__.py", line 6, in
<module>*
*File "build/bdist.macosx-10.3-fat/egg/Quartz/CoreGraphics/__init__.py",
line 9, in <module>*
*File "build/bdist.macosx-10.3-fat/egg/CoreFoundation/__init__.py", line 19,
in <module>*
*File "/Users/rjagodic/dev/SagePointer/sagePointer/Sage
Pointer.app/Contents/Resources/lib/python2.6/objc/_bridgesupport.py", line
156, in initFrameworkWrapper*
*File "/Users/rjagodic/dev/SagePointer/sagePointer/Sage
Pointer.app/Contents/Resources/lib/python2.6/objc/_bridgesupport.py", line
58, in _parseBridgeSupport*
*ValueError: Don't know CF type for typestr '^{__CFAllocator=}', cannot
create special wrapper*
*
*
However, when I run the app from the command line using "python myapp.py",
it runs perfectly. I tried searching about this but came up with nothing.
Any ideas?

Here's what I am using:
- Snow Leopard
- macPython 2.6.4  (NOT the system one)
- py2app 0.4.4 checked out from svn and compiled for the above python
- easy_install for the above python (NOT the system one)
- pyobjc installed for the above python using the above easy_install
pyobjc==2.2

Any help would be appreciated.
Thank you,
Ratko

Re: [Pyobjc-dev] objc 2.2 and libxml2?

[Glenn <grp...@so...>]

Thanks Ron.

For the benefit of other newbies like me: I downloaded the pyobjc-core  
tarball from http://pypi.python.org/pypi/pyobjc-core/2.2, cd'ed into  
the unzipped directory and then did the usual sudo setup.py install.  
PyObjC is behaving well for me now as I work through the excellent  
tutorial http://lethain.com/entry/2008/aug/22/an-epic-introduction-to-pyobjc-and-cocoa/ 
  .

Glenn

On Dec 8, 2009, at 12:38 PM, Ronald Oussoren wrote:

>
> On 8 Dec, 2009, at 19:50, Glenn wrote:
>
>> Hi,
>>
>> I've done a framework install of Python 2.6 on OSX10.5 and it works  
>> just fine.
>>
>> To enable Cocoa/Python apps, I've installed pyobjc 2.2 and that  
>> works well enough that the native MacOSX backend in matplotlib runs  
>> properly.
>>
>> However, when I try running my own app with Xcode, I get the  
>> following traceback:
>>
>> [Session started at 2009-12-08 10:24:30 -0800.]
>> Traceback (most recent call last):
>>   File "main.py", line 10, in <module>
>>     import objc
>>   File "/Library/Frameworks/Python.framework/Versions/2.6/lib/ 
>> python2.6/site-packages/pyobjc_core-2.2-py2.6-macosx-10.3-fat.egg/ 
>> objc/__init__.py", line 22, in <module>
>>     _update()
>>   File "/Library/Frameworks/Python.framework/Versions/2.6/lib/ 
>> python2.6/site-packages/pyobjc_core-2.2-py2.6-macosx-10.3-fat.egg/ 
>> objc/__init__.py", line 19, in _update
>>     import _objc
>> ImportError: dlopen(/Library/Frameworks/Python.framework/Versions/ 
>> 2.6/lib/python2.6/site-packages/pyobjc_core-2.2-py2.6-macosx-10.3- 
>> fat.egg/objc/_objc.so, 2): Library not loaded: /usr/lib/ 
>> libxml2.2.dylib
>>   Referenced from: /Library/Frameworks/Python.framework/Versions/ 
>> 2.6/lib/python2.6/site-packages/pyobjc_core-2.2-py2.6-macosx-10.3- 
>> fat.egg/objc/_objc.so
>>   Reason: Incompatible library version: _objc.so requires version  
>> 10.0.0 or later, but libxml2.2.dylib provides version 9.0.0
>> 2009-12-08 10:24:30.364 py1[960:10b] *** Terminating app due to  
>> uncaught exception 'NSInternalInconsistencyException', reason: '/ 
>> Users/glenn/learningcocoa/py1/main.m:44 main() PyRun_SimpleFile  
>> failed with file '/Users/glenn/learningcocoa/py1/build/Debug/ 
>> py1.app/Contents/Resources/main.py'.  See console for errors.'
>>
>> So, to fix this, I installed the latest version of libxml2.2.dylib  
>> in /usr/local/lib. Unfortunately, subsequent installation of the  
>> latest distribution of Pyobjc doesn't fix the problem:
>>
>> easy_install pyobjc==2.2  =>  /Library/Frameworks/Python.framework/ 
>> Versions/2.6/lib/python2.6/site-packages/pyobjc_core-2.2-py2.6- 
>> macosx-10.3-fat.egg
>>
>> because that contains a precompiled _objc.so that is linked to /usr/ 
>> lib/libxml2.2.dylib.
>>
>> What is the canonical way to get a framework install of pyobjc 2.2  
>> working properly in Python 2.6 on OS-X 10.5? I've read horror  
>> stories about breaking system apps if /usr/lib/libxml2.2.dylib is  
>> messed with.
>
> The release binaries were created on 10.6, which appearently ships  
> with an updated version of libxml.
>
> The easiest workaround for now is to download the source archive of  
> pyobjc-core and install that, easy_install pyobjc==2.2 should then  
> install the framework wrappers.
>
> What really sucks is that both the 10.5 and 10.6 versions of libxml  
> are of the 2.2 branch of libxml, which AFAIK should be binary  
> compatible :-(
>
> Ronald

Re: [Pyobjc-dev] objc 2.2 and libxml2?

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

On 8 Dec, 2009, at 19:50, Glenn wrote:

> Hi,
> 
> I've done a framework install of Python 2.6 on OSX10.5 and it works just fine. 
> 
> To enable Cocoa/Python apps, I've installed pyobjc 2.2 and that works well enough that the native MacOSX backend in matplotlib runs properly.
> 
> However, when I try running my own app with Xcode, I get the following traceback: 
> 
> [Session started at 2009-12-08 10:24:30 -0800.]
> Traceback (most recent call last):
>   File "main.py", line 10, in <module>
>     import objc
>   File "/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/pyobjc_core-2.2-py2.6-macosx-10.3-fat.egg/objc/__init__.py", line 22, in <module>
>     _update()
>   File "/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/pyobjc_core-2.2-py2.6-macosx-10.3-fat.egg/objc/__init__.py", line 19, in _update
>     import _objc
> ImportError: dlopen(/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/pyobjc_core-2.2-py2.6-macosx-10.3-fat.egg/objc/_objc.so, 2): Library not loaded: /usr/lib/libxml2.2.dylib
>   Referenced from: /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/pyobjc_core-2.2-py2.6-macosx-10.3-fat.egg/objc/_objc.so
>   Reason: Incompatible library version: _objc.so requires version 10.0.0 or later, but libxml2.2.dylib provides version 9.0.0
> 2009-12-08 10:24:30.364 py1[960:10b] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: '/Users/glenn/learningcocoa/py1/main.m:44 main() PyRun_SimpleFile failed with file '/Users/glenn/learningcocoa/py1/build/Debug/py1.app/Contents/Resources/main.py'.  See console for errors.'
> 
> So, to fix this, I installed the latest version of libxml2.2.dylib in /usr/local/lib. Unfortunately, subsequent installation of the latest distribution of Pyobjc doesn't fix the problem:
> 
> easy_install pyobjc==2.2  =>  /Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/pyobjc_core-2.2-py2.6-macosx-10.3-fat.egg
> 
> because that contains a precompiled _objc.so that is linked to /usr/lib/libxml2.2.dylib.
> 
> What is the canonical way to get a framework install of pyobjc 2.2 working properly in Python 2.6 on OS-X 10.5? I've read horror stories about breaking system apps if /usr/lib/libxml2.2.dylib is messed with.

The release binaries were created on 10.6, which appearently ships with an updated version of libxml.

The easiest workaround for now is to download the source archive of pyobjc-core and install that, easy_install pyobjc==2.2 should then install the framework wrappers.

What really sucks is that both the 10.5 and 10.6 versions of libxml are of the 2.2 branch of libxml, which AFAIK should be binary compatible :-(

Ronald

[Pyobjc-dev] objc 2.2 and libxml2?

[Glenn <grp...@so...>]

Hi,

I've done a framework install of Python 2.6 on OSX10.5 and it works  
just fine.

To enable Cocoa/Python apps, I've installed pyobjc 2.2 and that works  
well enough that the native MacOSX backend in matplotlib runs properly.

However, when I try running my own app with Xcode, I get the following  
traceback:

[Session started at 2009-12-08 10:24:30 -0800.]
Traceback (most recent call last):
   File "main.py", line 10, in <module>
     import objc
   File "/Library/Frameworks/Python.framework/Versions/2.6/lib/ 
python2.6/site-packages/pyobjc_core-2.2-py2.6-macosx-10.3-fat.egg/objc/ 
__init__.py", line 22, in <module>
     _update()
   File "/Library/Frameworks/Python.framework/Versions/2.6/lib/ 
python2.6/site-packages/pyobjc_core-2.2-py2.6-macosx-10.3-fat.egg/objc/ 
__init__.py", line 19, in _update
     import _objc
ImportError: dlopen(/Library/Frameworks/Python.framework/Versions/2.6/ 
lib/python2.6/site-packages/pyobjc_core-2.2-py2.6-macosx-10.3-fat.egg/ 
objc/_objc.so, 2): Library not loaded: /usr/lib/libxml2.2.dylib
   Referenced from: /Library/Frameworks/Python.framework/Versions/2.6/ 
lib/python2.6/site-packages/pyobjc_core-2.2-py2.6-macosx-10.3-fat.egg/ 
objc/_objc.so
   Reason: Incompatible library version: _objc.so requires version  
10.0.0 or later, but libxml2.2.dylib provides version 9.0.0
2009-12-08 10:24:30.364 py1[960:10b] *** Terminating app due to  
uncaught exception 'NSInternalInconsistencyException', reason: '/Users/ 
glenn/learningcocoa/py1/main.m:44 main() PyRun_SimpleFile failed with  
file '/Users/glenn/learningcocoa/py1/build/Debug/py1.app/Contents/ 
Resources/main.py'.  See console for errors.'

So, to fix this, I installed the latest version of libxml2.2.dylib in / 
usr/local/lib. Unfortunately, subsequent installation of the latest  
distribution of Pyobjc doesn't fix the problem:

easy_install pyobjc==2.2  =>  /Library/Frameworks/Python.framework/ 
Versions/2.6/lib/python2.6/site-packages/pyobjc_core-2.2-py2.6- 
macosx-10.3-fat.egg

because that contains a precompiled _objc.so that is linked to /usr/ 
lib/libxml2.2.dylib.

What is the canonical way to get a framework install of pyobjc 2.2  
working properly in Python 2.6 on OS-X 10.5? I've read horror stories  
about breaking system apps if /usr/lib/libxml2.2.dylib is messed with.

Glenn

Re: [Pyobjc-dev] Seeing a traceback

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

On 5 Dec, 2009, at 7:34, Orestis Markou wrote:

> 
> On 5 Dec 2009, at 01:37, Saptarshi Guha wrote:
> 
>> Hello,
>> When running my PyObjc app, I get some errors, but no traceback
>> 
>> e.g in the console (XCode's)
>> 
>> 2009-12-04 18:32:31.643 Awake[5689:10b] Awake did finish launching.
>> 2009-12-04 18:32:31.644 Awake[5689:10b] Using the following
>> wakeupfile:/Users/yanger/.wakeuprc
>> 2009-12-04 18:32:31.653 Awake[5689:10b] <type 'exceptions.TypeError'>:
>> 'NoneType' object is not iterable
>> 
>> But I'd like to see the traceback for the last line. Is there  a way
>> for me to view it?
>> Regards
>> Saptarshi
>> PYObjc on leopard 10.5.8 (Macbook)
> 
> import objc
> objc.setVerbose(True)
> 
> This should be the default behaviour, IMO.

The reason this isn't the default behaviour is that it will log all exceptions, even perfectly valid ones that are caught later on.

Ronald

Re: [Pyobjc-dev] Seeing a traceback

[Saptarshi G. <sap...@gm...>]

Thanks, worked perfectly.
Regards
Saptarshi

>
> import objc
> objc.setVerbose(True)
>
> This should be the default behaviour, IMO.
>
> Orestis
>

Re: [Pyobjc-dev] Seeing a traceback

[Orestis M. <or...@or...>]

On 5 Dec 2009, at 01:37, Saptarshi Guha wrote:

> Hello,
> When running my PyObjc app, I get some errors, but no traceback
> 
> e.g in the console (XCode's)
> 
> 2009-12-04 18:32:31.643 Awake[5689:10b] Awake did finish launching.
> 2009-12-04 18:32:31.644 Awake[5689:10b] Using the following
> wakeupfile:/Users/yanger/.wakeuprc
> 2009-12-04 18:32:31.653 Awake[5689:10b] <type 'exceptions.TypeError'>:
> 'NoneType' object is not iterable
> 
> But I'd like to see the traceback for the last line. Is there  a way
> for me to view it?
> Regards
> Saptarshi
> PYObjc on leopard 10.5.8 (Macbook)

import objc
objc.setVerbose(True)

This should be the default behaviour, IMO.

Orestis

Re: [Pyobjc-dev] Seeing a traceback

[Anders H. <bo...@ki...>]

I agree this is pretty annoying and I think a pretty bad default
behavior. A workaround that I used recently is you make a try/except
block around all the code in the method you are interested in (in this
case I guess applicationDidFinishLaunching_ or similar) and do:

import traceback
traceback.print_exc()

Best Regards,
Anders Hovmöller

PS. Funnily enough I copied that code from a program I am writing
called "waker", are you also writing some alarm clock system? Send me
an email in that case, it'd be fun to discuss different approaches :P

On Sat, Dec 5, 2009 at 12:37 AM, Saptarshi Guha
<sap...@gm...> wrote:
> Hello,
> When running my PyObjc app, I get some errors, but no traceback
>
> e.g in the console (XCode's)
>
> 2009-12-04 18:32:31.643 Awake[5689:10b] Awake did finish launching.
> 2009-12-04 18:32:31.644 Awake[5689:10b] Using the following
> wakeupfile:/Users/yanger/.wakeuprc
> 2009-12-04 18:32:31.653 Awake[5689:10b] <type 'exceptions.TypeError'>:
> 'NoneType' object is not iterable
>
> But I'd like to see the traceback for the last line. Is there  a way
> for me to view it?
> Regards
> Saptarshi
> PYObjc on leopard 10.5.8 (Macbook)
>
> ------------------------------------------------------------------------------
> Join us December 9, 2009 for the Red Hat Virtual Experience,
> a free event focused on virtualization and cloud computing.
> Attend in-depth sessions from your desk. Your couch. Anywhere.
> http://p.sf.net/sfu/redhat-sfdev2dev
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev
>