[Zope-Coders] Re: [Zope-Checkins] CVS: Zope - z2.py:1.62

[Matt Behrens]

On Mon, Apr 29, 2002 at 10:34:20AM +0100, Toby Dickenson wrote:

> I can think of two reasons why that would become the preferred method of 
> operation:
> 
> 1. It is readable, extensible, and clean.

Yes.  Paul suggested ConfigParser to me and I haven't looked back.
(THANKS PAUL!)

> 2. One of the other options is gratuitously incompatible with
>    long options ;-)

Certainly, but at the time it was OK. :-)

> Does this work:
> 
> * z2.py continues to support the same command line options as 2.5, for
>   backwards compatability only.

Yes, I think this is an immutable goal.  I think I am going to add
'-o' to the list of options, for feeding in run-time overrides.

I do not believe this is scope creep, but someone pleasefeel free
to slap me silly if it is.

> * Everything new (including icp) uses instance.conf _only_

Certainly.  instance.conf is also slated to replace the host of
environment variables used to tweak behavior of various things, see
my next message I'm about to compose...

> * Leave --icp in its current incompatible-with-zctl form, for the benefit
>   of people using "z2.py --icp" until they make the transition to
>   instance.conf

Yeah, if we don't worry about zctl, that works.