Re: [Pyobjc-dev] AppKit vs. import *
Brought to you by:
ronaldoussoren
From: Bob I. <bo...@re...> - 2005-05-29 18:37:31
|
On May 29, 2005, at 6:50 AM, Ronald Oussoren wrote: > > On 29-mei-2005, at 13:38, Just van Rossum wrote: > > >> Isn't the AppKit module supposed to support the "import *" idiom? It >> currently exports a class named "List", which caused some >> confusion with >> a custom class we have named "List" (which isn't an NSObject >> subclass). >> AppKit also exports some other dodgy stuff: >> > > List is defined in the objc runtime '@interface List : Object'. I'm > not entirely happy about exporting all classes from every wrapper > module, this was introduced to reduce the amount of time that is > needed > for the initial import of frameworks and therefore the startup time of > PyObjC based programs. It was also done for parity with Objective-C. If we only import symbols from the bundle itself, symbols from embedded frameworks and dependencies will be missed, which is certainly not the case in Objective-C. I really do not want to see this behavior change. Typically the pattern you should use is to "import *" from your Objective-C dependencies first, and then import from your Python modules. -bob |