[Pyobjc-dev] re PyObjC Debuggin Best Practices

[Daniel L. <da...@br...>]

Well, seeing as no one answered at all (except one other soul looking for
information), I am assuming that there isn't anything substantial.
So for my apps, to maximize the size of my tool set, I have decided to
minimize the PyObj portions as much as possible (just the View and small UI
Controllers and Models where handy like tables, etc. ) and implement the
rest of the code in standalone straight Python classes which I can
source-level debug easily in Komodo using unit tests. I can debug the UI in
Xcode and then when I combine everything in Xcode, I only have small bits of
code that are opaque to source-level debugging if I even need it. Now that I
think about it, that makes the most sense anyway. Assuming py2app does the
right things with XCode builds to bring in third-party modules like
appscript which I like to use a lot--I've been "chickening out" so far and
writing a setup and using py2app from the command line.
I am sure I can figure out how to add the scripting to XCode as a shell
script at some point.

I might try Eclipse are well, but I have become used to Komodo after a year
or so of using it and so reluctant to tackle the Eclipse learning curve
unless it offers more than Komodo. Komodo works great for wxPython debugging
and I may just use wxPython instead of PyObjC for UI components. I am
concerned that PyObjC is second-class on OS X just like the Java-Cocoa
bridge was--and we all know how that turned out in the end. Anyone know of
any commitments to do so, or is PyObjC reached its zenith given Apple is
dropping other non-Cocoa things such as public Carbon-64 to focus on Cocoa?

Don't get me wrong, I appreciate Apple supporting Python so well in the
first place, and they've improved integration in Xcode 3.0. I just wish
they'd gone farther with it.