[Pyobjc-dev] top level namespaces

[Bill B. <bb...@co...>]

On Saturday, Feb 1, 2003, at 15:02 US/Eastern, Tony Lownds wrote:
> Hi,
> At 2:15 PM -0500 2/1/03, Bill Bumgarner wrote:
>> As Just mentioned, it is about time to do a 0.9 release.
> Out of curiosity, will 0.9 be FFI only?

Good question.   Personally, I think it should be for two reasons:

- we have FFI only features now [classAddMethods]

- we have already had a situation where the non-FFI stuff broke because 
it went untested... i.e. non-FFI support is being neglected by the dev 
team.

>> If we are going to do any major changes to the namespace, now is the 
>> time.
>>
>> I would like to see *everything* in pyobjc move into a 'pyobjc' 
>> package... and have the other three/four packages hang below that.
>>
>> pyobjc.obj
>> pyobjc.foundation
>> pyobjc.appkit
>> pyobjc.addressbook
>
> lowercase for appkit and foundation?

Follows Python standard?     Personally, I like Foundation and AppKit, 
as well -- of course, AppKit really should be Cocoa for OS X even 
though Cocoa is basically an empty framework...

>> ... etc ...
>>
>> This will make for much easier packaging in app wrappers [simplifies 
>> build targets] and much less clutter in site-packages.
>>
>> thoughts?
>
> FWIW, I am -0
>
> 1. The current flat nesting adds weight to the idea that Foundation 
> and AppKit are big frameworks in their own right

I still think they should be nested, just under a single roof....

> 2. This adds some text for every import (and there tend to be a lot in 
> pyobjc programs)

True.

> 3. Its not hard to package the modules in a subdirectory, using .pth 
> files in /usr/lib/site-packages and with minimal extra code in 
> bin-python-main.m. Hmm, and some extra code in bundlebuilder.py too, I 
> think. OTOH, extra code somewhere is still extra code, and putting 
> everything in a package doesn't require any extra code.

I'm not sure what this means....

> 4. If I see "Declared in: AppKit/NSMatrix.h" in Apple's docs, I write:
> "from AppKit import NSMatrix". One-to-one correspondence!

Which would change to:

     from pyobjc.AppKit import NSMatrix

Strictly speaking, this emphasizes that one is using the 'pyobjc' 
gateway into the 'AppKit' framework -- a more correct nomenclature 
because the pyobjc bridge changes the way the AppKit is accessed.

 > Just my 2 cents...

Thanks...

All in all, I'm not hugely attached to any of this.   I suppose my 
motivation is largely one of having to uninstall the module 
semi-regularly to ensure that standalone builds still work correctly.   
Not a very good reason to modify the dev environment, certainly.

b.bum