From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28494 invoked by alias); 27 Oct 2011 17:01:36 -0000 Received: (qmail 28449 invoked by uid 22791); 27 Oct 2011 17:01:33 -0000 X-SWARE-Spam-Status: No, hits=-7.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 27 Oct 2011 17:01:14 +0000 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p9RH1Cmw007702 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 27 Oct 2011 13:01:13 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id p9RH1CeW013090; Thu, 27 Oct 2011 13:01:12 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id p9RH1AJJ003956; Thu, 27 Oct 2011 13:01:11 -0400 From: Tom Tromey To: Robert Lupton the Good Cc: gdb@sourceware.org Subject: Re: Option parsing in gdb python References: <1319403653.11425.ezmlm@sourceware.org> <1C69408D-CEF9-4B86-A2E2-4A7547F069D9@astro.princeton.edu> Date: Thu, 27 Oct 2011 19:32:00 -0000 In-Reply-To: <1C69408D-CEF9-4B86-A2E2-4A7547F069D9@astro.princeton.edu> (Robert Lupton the Good's message of "Mon, 24 Oct 2011 17:05:51 -0400") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.90 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2011-10/txt/msg00204.txt.bz2 >>>>> "Robert" == Robert Lupton the Good writes: Robert> I can do this (and did; read on, Dear Reader). Does gdb python Robert> have a position on python 2.6 support? If so, and if gdb Robert> accepts this parser, we should provide both and wrap the imports Robert> in try blocks I think something like this would be worthwhile. The bar is reasonably high for getting stuff into gdb. You need copyright assignment papers for non-trivial additions; plus documentation and a test case. Tom