[Pyobjc-dev] pyobjc-0.6 with Python2.2 and message debugging

[Steven D. M. <sd...@mi...>]

[1] pyobjc will build for Python2.2, but there is a bug in 2.2 that
 needs to be fixed. (This is fixed in CVS)

http://sourceforge.net/tracker/?group_id=5470&atid=105470&func=detail&aid=498915

[This has been discussed further on pythonmac-sig]


For debugging, I have found that setting instrumentObjcMessageSends()
causes a trace of all object messages to be dumped to a /tmp file.
I've put a line in pyobjc ObjC.m to turn on tracing if the -v
(PYTHONVERBOSE) flag it set. This will go into the next release,
but below is a diff if anyone wants it before then.

-- Steve Majewski


*** ObjC.m      Mon Jan 21 17:03:28 2002
--- ObjC.m.0    Mon Jan 21 17:00:52 2002
***************
*** 146,153 ****
    [OC_PythonBundle class];

    ObjCObject_initialize();
-
-   if (Py_VerboseFlag) instrumentObjcMessageSends(1);

    if (PyErr_Occurred())
      Py_FatalError ("can't initialize module pyobjc");
--- 146,151 ----