From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3965 invoked by alias); 7 Sep 2012 14:27:00 -0000 Received: (qmail 3956 invoked by uid 22791); 7 Sep 2012 14:26:59 -0000 X-SWARE-Spam-Status: No, hits=-3.3 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from server-nat-6.cs.umd.edu (HELO bacon.cs.umd.edu) (128.8.127.149) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 07 Sep 2012 14:26:47 +0000 Received: from wireless-206-196-167-133.umd.edu (wireless-206-196-167-133.umd.edu [206.196.167.133]) (Authenticated sender: khooyp) by bacon.cs.umd.edu (Postfix) with ESMTPSA id 590CAB402D5; Fri, 7 Sep 2012 10:26:35 -0400 (EDT) Subject: Re: [RFC] Make python/lib/gdb and submodules proper Python modules Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Khoo Yit Phang In-Reply-To: Date: Fri, 07 Sep 2012 14:27:00 -0000 Cc: Khoo Yit Phang , GDB Patches Content-Transfer-Encoding: quoted-printable Message-Id: <979CE4F9-537E-4FA0-893D-FDF19CB408F7@cs.umd.edu> References: To: Doug Evans X-CSD-MailScanner-ID: 590CAB402D5.A996B X-CSD-MailScanner: Found to be clean X-CSD-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-50, required 5, autolearn=not spam, ALL_TRUSTED -50.00) X-CSD-MailScanner-From: khooyp@cs.umd.edu X-CSD-MailScanner-Watermark: 1347632796.23686@sgJVle1HyN8Q6LxCmE6cog Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-09/txt/msg00067.txt.bz2 Hi, (Sorry for the resend again!) On Sep 7, 2012, at 2:18 AM, Doug Evans wrote: > On Sun, Sep 2, 2012 at 8:44 PM, Khoo Yit Phang wrote: >>=20 >> One caveat about this patch is that the data-directory must contain the >> gdb module, otherwise Python will not be fully initialized (with a warni= ng) >> and Python support will be very limited (only the _gdb module will be >> available). >=20 > One thing that comes to mind is that, regardless of implementation > details, we can't easily get rid of gdb.PYTHONDIR because it's part of > the API gdb provides. > [grep PYTHONDIR doc/gdb.texinfo] It's pretty easy to restore PYTHONDIR if necessary, by computing it from gd= b.__file__. I'm more concerned about the caveat about requiring the initial= data-directory for Python. Is it common to change the data-directory, othe= r than for testing GDB? Yit September 7, 2012