From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22674 invoked by alias); 12 Jan 2012 17:46:12 -0000 Received: (qmail 22664 invoked by uid 22791); 12 Jan 2012 17:46:11 -0000 X-SWARE-Spam-Status: No, hits=-3.2 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,RCVD_IN_DNSWL_LOW,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail-vx0-f169.google.com (HELO mail-vx0-f169.google.com) (209.85.220.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 12 Jan 2012 17:45:58 +0000 Received: by vcge1 with SMTP id e1so1834189vcg.0 for ; Thu, 12 Jan 2012 09:45:57 -0800 (PST) Received: by 10.221.13.135 with SMTP id pm7mr2700694vcb.51.1326390357683; Thu, 12 Jan 2012 09:45:57 -0800 (PST) MIME-Version: 1.0 Received: by 10.221.13.135 with SMTP id pm7mr2700682vcb.51.1326390357484; Thu, 12 Jan 2012 09:45:57 -0800 (PST) Received: by 10.220.229.1 with HTTP; Thu, 12 Jan 2012 09:45:57 -0800 (PST) In-Reply-To: References: <09787EF419216C41A903FD14EE5506DD030F1EB39B@AUSX7MCPC103.AMER.DELL.COM> <09787EF419216C41A903FD14EE5506DD030F1EB45D@AUSX7MCPC103.AMER.DELL.COM> Date: Thu, 12 Jan 2012 17:48:00 -0000 Message-ID: Subject: Re: Make the "python" command resemble the standard Python interpreter From: Doug Evans To: Paul_Koning@dell.com Cc: khooyp@cs.umd.edu, gdb-patches@sourceware.org X-System-Of-Record: true Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes 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-01/txt/msg00417.txt.bz2 On Thu, Jan 12, 2012 at 9:38 AM, Doug Evans wrote: > On Thu, Jan 12, 2012 at 9:30 AM, =A0 wrote: >> Yes, but I think the benefits outweigh the small imcompatibility. > > Yes and no. > - I may want a script that invokes python interactively. > - How do I write a gdb macro that invokes the python repl? > > Solve those problems, and provide a migration path away from the old > behaviour, and then you've got something. As a strawman, a new command, python-foo, could be provided [python-code? python-script?] that had the "old" behaviour. As for migration, we *could* add python-foo as an alias for python to 7.4 (seems safe enough) and say the "python" command will change it's behaviour in 7.5 (or some such). Or we could just skip the first step and just say python will change incompatibly in 7.5. [I don't have a preference, but I think we need to start doing this kind of thing, and this would be good practice. :-)]