Return-Path: Mailing-List: contact gump-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list gump@jakarta.apache.org Received: (qmail 94720 invoked from network); 24 Apr 2003 08:10:18 -0000 Received: from host190-154.pool80204.interbusiness.it (HELO PC103) (80.204.154.190) by daedalus.apache.org with SMTP; 24 Apr 2003 08:10:18 -0000 Message-ID: <3EA79BC9.2020908@apache.org> Date: Thu, 24 Apr 2003 10:09:45 +0200 From: Nicola Ken Barozzi Reply-To: nicolaken@apache.org Organization: Apache Software Foundation User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gump code and data Subject: Re: [PATCH][gump.py] Refactoring and fixes References: <008e01c308f7$6d9bd7a0$c01ce641@wdn086> <3EA651C0.5010507@apache.org> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-GCMulti: 1 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Sam Ruby wrote, On 23/04/2003 13.11: > Nicola Ken Barozzi wrote: ... >> gumputil.py - utility code, like property load and file caching >> gump.cfg - gump conf > > Instead of a cfg file, this can simply be pure python. Making it python > would make it more powerful in terms of what expressions are allowed in > the file. And easier to access from the code (no getGumpConfig calls). > > Look at my config file for my weblogging software: > > http://www.intertwingly.net/code/mombo/config.py Now I remember why I did it in the first place. I was tinkering with py2exe because I thought of distributing Gump as precompiled exes, so a file config was the only way. But now I think that we should simply tell our users to install python, so that they can eventually modify Gump itself. If we give binaries, it would probably reduce the possible Gump code herlpers. Just FYI. -- Nicola Ken Barozzi nicolaken@apache.org - verba volant, scripta manent - (discussions get forgotten, just code remains) ---------------------------------------------------------------------