Re: [Pyobjc-dev] experiences using pyobjc+pychecker?
Brought to you by:
ronaldoussoren
From: Ronald O. <ous...@ci...> - 2003-11-19 21:45:25
|
On 19 nov 2003, at 22:11, David Eppstein wrote: > Hi, is anyone else using pychecker and pyobjc together successfully? probably not, there's a bug in PyObjC that makes that impossible:-(. A script containing nothing but 'import Foundation' is enough to crash the interpreter when using pychecker. I've checked in a partial fix for this problem, your script can now be checked but my almost empty script gives odd warnings: 2003-11-19 22:36:52.721 python[24062] *** *** Selector 'instancesRespondToSelector:' sent to dealloced instance 0xa0a04e10 of class UNKNOWN. Break at '-[_NSZombie methodSignatureForSelector:]' to debug. 2003-11-19 22:36:52.724 python[24062] *** *** Selector 'func:code' sent to dealloced instance 0xa0a04e10 of class UNKNOWN. Break at '-[_NSZombie methodSignatureForSelector:]' to debug. 2003-11-19 22:36:52.730 python[24062] *** *** Selector 'instancesRespondToSelector:' sent to dealloced instance 0xa0a04e10 of class UNKNOWN. Break at '-[_NSZombie methodSignatureForSelector:]' to debug. 2003-11-19 22:36:52.733 python[24062] *** *** Selector 'instanceMethodSignatureForSelector:' sent to dealloced instance 0xa0a04e10 of class UNKNOWN. Break at '-[_NSZombie methodSignatureForSelector:]' to debug. This is probably a bug in PyObjC. BTW. the crash was caused by getattr(..., 'func_code'). This probably means that pychecker won't be able to check if you use the right number of arguments for calls to ObjC methods. Ronald |