Re: [Pyobjc-dev] pyobjc/Tools vs. pyobjc/Scripts

[Just v. R. <ju...@le...>]

bb...@ma... wrote:

> I have no particular affection for any of this.
> 
> One opinion:  I would like to see a series of scripts that wrap the 
> various tools found in other parts of the module-- some of which is in 
> Lib/*/*-- such that the scripts are installed into /usr/local/bin/ (or 
> /usr/bin/) as per a normal install.
> 
> I don't like scripts that act as a module in one form and a command 
> line tool in another.   I would much rather the command line driver 
> part simply use the separate module -- it keeps the module clean and 
> moves all the command line arg processing/validation to an isolated 
> spot that provides an excellent and clean example of how to work with 
> the module.

Hm, maybe. I prefer to keep things together unless they become too big.
NibClassBuilder isn't all that big I think.

> The auto-nib stuff that can dump a class template is a perfect 
> example....

Hm, I'd agree from the standpoint that this module isn't readily accessible as a
command line too. Why not add a script to Scripts that goes like this:

#!/usr/bin/env python
from AppKit import NibClassBuilder
NibClassBuilder.commandline()

Add it to setup.py as a script and it'll be installed globally, too.

Just