Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Phil Muldoon <pmuldoon@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/4]: Make "python" start a standard Python prompt
Date: Wed, 25 Jul 2012 06:45:00 -0000	[thread overview]
Message-ID: <500F95FB.5060904@redhat.com> (raw)
In-Reply-To: <770F6E2B-70F5-4DF9-8E01-BD4F5FDC7AB1@cs.umd.edu>

On 07/16/2012 09:47 PM, Khoo Yit Phang wrote:
> Hi,
> 
> I'd like to resubmit my patches to make the "python" command start a standard Python prompt (I've completed the copyright assignment). As discussed back in January-February (http://permalink.gmane.org/gmane.comp.gdb.patches/71971), I've updated my patch to move the old "python" to "python-block".


Apologies for the delay, I've been mulling if this constitutes an API
change.  Because we have an API promise, we cannot materially alter
the behavior of an API without providing compatibility that is
transparent and automatic for older scripts.  

I am not sure what the implication for your change is.  If a user has
a script (or some code in .gdbinit, or whatever ) that uses "python"
will it break that user's script?  If so it is probably better to leave
python as it is, and use python-interactive (or whatever) for the
interactive prompt.  Judging that you changed the testsuite to use
python-block, I am guessing it is a material and non-compatible
change? I guess I need more data, testing.  I am replying here now as
you pinged the patch (which is totally fine, just updating you).

Cheers

Phil


  parent reply	other threads:[~2012-07-25  6:45 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-16 20:47 Khoo Yit Phang
2012-07-24 21:19 ` Khoo Yit Phang
2012-07-25  6:45 ` Phil Muldoon [this message]
2012-07-25 16:18   ` Tom Tromey
2012-07-25 16:58     ` Khoo Yit Phang
2012-07-25 17:20       ` Matt Rice
2012-07-25 17:29         ` Khoo Yit Phang
2012-07-25 17:43       ` Tom Tromey
2012-07-25 17:55         ` Khoo Yit Phang
2012-07-25 17:59           ` Tom Tromey
2012-07-25 21:07             ` Khoo Yit Phang
2012-07-26 17:38               ` Tom Tromey
2012-07-26 17:52                 ` Khoo Yit Phang
2012-07-26 18:06                   ` Eli Zaretskii
2012-07-26 18:10                     ` Khoo Yit Phang
2012-07-27  2:32                       ` Khoo Yit Phang
2012-07-27 19:23                         ` Tom Tromey
2012-07-28  6:53                         ` Eli Zaretskii
2012-07-28 14:35                           ` Khoo Yit Phang
2012-07-28 15:05                             ` Eli Zaretskii
2012-07-28 15:14                               ` Khoo Yit Phang
2012-07-31 22:04                                 ` Khoo Yit Phang
2012-08-01 15:46                                   ` Tom Tromey
2012-08-10 17:28                                     ` Khoo Yit Phang
2012-08-22 17:44                                   ` Khoo Yit Phang
2012-08-22 17:59                                     ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=500F95FB.5060904@redhat.com \
    --to=pmuldoon@redhat.com \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox