Re: NSObject, doctest
Erik van Blokland <[email protected]> Sun, 23 Feb 2014 09:05:11 +0100
| Newsgroups | gmane.comp.python.pyobjc.devel |
|---|---|
| Message-ID | <[email protected]> |
On 19 dec. 2013, at 13:42, Ronald Oussoren <[email protected]> wrote: >> >> Is there something in the nature of pyobjc objects that makes them confuse dockets? > > Not sure if the class repr at the top of the traceback is relevant, but if it is this might be due to doctest trying to test some PyObjC classes. > > BTW. I’m moving away from “from AppKit import *” towards just importing what I need. That leads to code that’s slightly easier to check with linting tools, and in recent versions of PyObjC is faster as well because the framework wrappers now try to do as little work as possible (and that doesn’t work when you import everything). I finally got around to rewriting the tests, for completeness' sake I can confirm that switching from AppKit import * to just the items I need allows the doctests to run. Thanks! E ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk