[Dev] application.Util.py status
morgen at osafoundation.org
Wed Dec 8 09:30:26 PST 2004
I added Util.py (better name suggestions welcome) because I was getting
tired of duplicating these methods in unit tests, schema documentation
generator, and any other script making use of the repository and parcel
manager outside of Chandler. I believe at the moment the methods in
Util.py are currently only being used by the schema documentation
generator, but the hope is that everything would eventually use it
(including Application.py). So yes, it's a migration in progress *to*
Util.py (or whatever name we pick).
On Dec 8, 2004, at 9:06 AM, John Anderson wrote:
> Startup option parsing should probably go in Application.py if it's
> part of Chandler startup.
> The startup stuff in Util.py is there only for unit tests, and I need
> to make a pass to simplify it and modify Application.py to also use
> it. I'll try to do it soon.
> Also, I'd be happy to review any changes you make to Application.py,
> since I wrote most of it.
> Mike Taylor wrote:
>> I'm going thru the Chandler startup process to see what is new and I
>> have a question :)
>> The routines in application/Util.py seem to be duplicated by code
>> inside of application/Application.py - is there a migration in
>> progress *to* Util.py or ???
>> If it's not a migration, then is there a need for Util.py. Should I
>> start looking into finishing the migration if it is?
>> The reason for me doing this is that I need to add some startup
>> option parsing code to allow me to continue with the linux installer
>> and, while scouting the best place for the new code, I came across
>> Util.py which seems to be a good spot for the code.
>> PGP Fingerprint = 9996 719F 973D B11B E111 D770 9331 E822 40B3 CD29
>> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>> Open Source Applications Foundation "Dev" mailing list
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> Open Source Applications Foundation "Dev" mailing list
More information about the Dev