Return-Path: Delivered-To: apmail-gump-general-archive@www.apache.org Received: (qmail 22643 invoked from network); 8 Jun 2004 21:26:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 8 Jun 2004 21:26:16 -0000 Received: (qmail 87609 invoked by uid 500); 8 Jun 2004 21:26:31 -0000 Delivered-To: apmail-gump-general-archive@gump.apache.org Received: (qmail 87568 invoked by uid 500); 8 Jun 2004 21:26:30 -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 87550 invoked by uid 99); 8 Jun 2004 21:26:30 -0000 Received: from [130.214.10.19] (HELO mx1.try.sybase.com) (130.214.10.19) by apache.org (qpsmtpd/0.27.1) with ESMTP; Tue, 08 Jun 2004 14:26:30 -0700 Received: from mail.try.sybase.com (mail.try.sybase.com [130.214.10.18]) by mx1.try.sybase.com (8.11.6/8.11.0) with ESMTP id i58KQc227277 for ; Tue, 8 Jun 2004 14:26:38 -0600 Received: from tsws1 ([10.22.120.60]) by mail.try.sybase.com (8.11.6/8.11.6) with SMTP id i58L48k19996 for ; Tue, 8 Jun 2004 15:04:08 -0600 Message-ID: <170f01c44d9f$354cf030$03bfea43@sybase.com> From: "Adam R. B. Jack" To: Subject: PROPOSAL: SAX+xmlutils -> xml.dom.minidom Date: Tue, 8 Jun 2004 15:25:58 -0600 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.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I just can't seem to deal with the code that Sam originally wrote for parsing/merging XML. I've spent days trying to develop unit tests, and get inside it. I think I have a clue how it is meant to operate/function, but the implementation is so 'tight'/Pythonic that I just can't get 100% with it. I am finding it infuriating. I can't fix the bugs that are there, I can't extend it without make more bugs, 'odd stuff' happens. I know there is risk in such a fundamental change, but I'd like to re-write it using simple DOM (unless Sam feels like stepping in & educating me in detail.) Basically the SAX events are used to construct DOM-like Python objects (maybe lighter weight, I'm not sure) so I don't see a lot of difference. Having Python DOM ought allow us to leverage XPATH and such, so has additional benefits. We use basic XML so ought be able to us Python's minidom. My suspicion is that if I do this we'll find subtle 'merge failures', certain merge features (like overriding projects, etc.), but few than the higher echelon Gumpmeisters would know how to use these anyway. That, and I personally believe that a lot are broken in Gumpy already, we've just not had bug reports 'cos they are obscure. I'll do this in a separate branch & perform runs on http://gump.try.sybase.com that we could review. I don't want to be working on this, but I can't seem to get past it. I don't want to be 'scared' of any part of Gump, and I want to be able to extend it/fix it. Thoughts? [BTW: I am trying to work on artefacts/repository, I just somehow got trapped in this. I guess the performance speed-up w/ removing Annotations just piqued my curiosity. I feel like a cat! ;) ] regards, Adam -- Experience the Unwired Enterprise: http://www.sybase.com/unwiredenterprise Try Sybase: http://www.try.sybase.com --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@gump.apache.org For additional commands, e-mail: general-help@gump.apache.org