Return-Path: Delivered-To: apmail-gump-general-archive@www.apache.org Received: (qmail 97159 invoked from network); 11 Jan 2005 14:15:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 11 Jan 2005 14:15:56 -0000 Received: (qmail 19899 invoked by uid 500); 11 Jan 2005 14:15:55 -0000 Delivered-To: apmail-gump-general-archive@gump.apache.org Received: (qmail 19869 invoked by uid 500); 11 Jan 2005 14:15:55 -0000 Mailing-List: contact general-help@gump.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Gump code and data" Reply-To: "Gump code and data" Delivered-To: mailing list general@gump.apache.org Received: (qmail 19854 invoked by uid 99); 11 Jan 2005 14:15:55 -0000 X-ASF-Spam-Status: No, hits=-10.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from minotaur.apache.org (HELO tsws1) (209.237.227.194) by apache.org (qpsmtpd/0.28) with SMTP; Tue, 11 Jan 2005 06:15:54 -0800 Message-ID: <03ec01c4f7e8$54bfdd30$6501a8c0@sybase.com> From: "Adam R. B. Jack" To: "Gump code and data" References: Subject: Re: Gump3 questions Date: Tue, 11 Jan 2005 07:06:21 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N > > 2) Does Gump3 use Zope or work with Zope? > > No, it doesn't use Zope. Why would you want to do that? Zope is overkill > IMNSHO and they made a lot of the wrong design decisions. I never suggested it, I was merely asking. Look for the word "zope" inside the Gump3 code to figure out why. ;-) > >>>> import testrunner > >>>> testrunner.main('-a') > > Nope. No idea. Try stepping through it in debug mode :-D Yeah, I did that yesterday. Unfortunately the debugger seems to request/set a command line, rather than work like the Python shell. It works in the debugger. Oh well, I'm just trying to be more Pythonic this time round, I'll figure it out. > IMNSHO the answer is a big fat "no". Experience shows that when it is > annoying to pass in lots of things into a component because it looks > visually ugly, you pass in less stuff, and that is a Good Thing. Trust me on > this. If you need to pass more than 5 things around between components > that's a problem. Good point. Hadn't considered it that way, but I sure did "feel" the resistence to pass stuff, so I hear ya... > > Also, tell folks the names of start/stop timing properties > > seems odd. Maybe we need to pass some pre-dictionaries of terms or > > something. > > I don't know what you're referring to here... class Dynagumper(AbstractPlugin): """ Populate the DynaGump run metadata database. """ def __init__(self, db, log, startdate_property_name='startdate', enddate_property_name='enddate'): and where thing fail 'cos getattr needs def visit_project(self, project): """Add information about a project to the database.""" tablename = "projects" startdate = getattr(project, self.startdate_property_name) <---- enddate = getattr(project, self.enddate_property_name) name = project.name What were you trying to achieve with this? If we start passing property names into component we'll blow past 5 like yesterday... regards Adam --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@gump.apache.org For additional commands, e-mail: general-help@gump.apache.org