From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Ken Manheimer" Newsgroups: gmane.emacs.devel Subject: Re: python.el fixes for Emacs 22 Date: Fri, 15 Feb 2008 17:21:47 -0500 Message-ID: <2cd46e7f0802151421g50139146ycfb4c32fbcc975ba@mail.gmail.com> References: <87ve4sqsqe.fsf@stupidchicken.com> <18356.54892.186541.669277@kahikatea.snap.net.nz> <861w7euz7a.fsf@lola.quinscape.zz> <2cd46e7f0802150943x46e9bcb0i4c3b6075d48cc979@mail.gmail.com> <18358.2182.671882.927824@kahikatea.snap.net.nz> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_591_21882573.1203114107636" X-Trace: ger.gmane.org 1203114132 5026 80.91.229.12 (15 Feb 2008 22:22:12 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 15 Feb 2008 22:22:12 +0000 (UTC) Cc: sdl.web@gmail.com, cyd@stupidchicken.com, rms@gnu.org, emacs-devel@gnu.org To: "Nick Roberts" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Feb 15 23:22:34 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JQ8wx-0000eY-3N for ged-emacs-devel@m.gmane.org; Fri, 15 Feb 2008 23:22:31 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JQ8wS-0000Xr-Dv for ged-emacs-devel@m.gmane.org; Fri, 15 Feb 2008 17:22:00 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JQ8wJ-0000Us-Pq for emacs-devel@gnu.org; Fri, 15 Feb 2008 17:21:52 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JQ8wI-0000TX-5f for emacs-devel@gnu.org; Fri, 15 Feb 2008 17:21:50 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JQ8wH-0000TO-DP for emacs-devel@gnu.org; Fri, 15 Feb 2008 17:21:49 -0500 Original-Received: from wa-out-1112.google.com ([209.85.146.183]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JQ8wG-0003ux-Oo for emacs-devel@gnu.org; Fri, 15 Feb 2008 17:21:49 -0500 Original-Received: by wa-out-1112.google.com with SMTP id k34so1436356wah.10 for ; Fri, 15 Feb 2008 14:21:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=IJBEjTSwoZ105qPxwcApbLics7VC09al7U4mbt/vHU0=; b=GaIcMMoHawrqAozIzpNptF5LzxMOMf3DhkgVdzkWvkLzW2hKdvxCT4hcQJLfmvoowOJXkOO/P8Cx84DP7ukWodh9OTpJCc51HjGmoC3k1m9kn6UGWRiAUovgaKlKIuL8GmPjdWQ7u9ODgE/waB2YM7B/5SLAOLdQqI8Zzgy3mcc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=nreYd3Kiy55BGMa/J0GAMr5Dni0+TTb7/FBsbaEjhj/U0qNCzQ+BHL3Bu7Z3BLxm/Yyew7mkMBiYoUwhVRTrU4V0YhKL9hU8geC3QpXtl4Zq3XpO3TsIhbThib3prkA0QwMjbAGxHQ0qrbI6eOptb+Ci990iiZOYP7AedzXa87Q= Original-Received: by 10.114.176.1 with SMTP id y1mr3534718wae.86.1203114107664; Fri, 15 Feb 2008 14:21:47 -0800 (PST) Original-Received: by 10.114.160.13 with HTTP; Fri, 15 Feb 2008 14:21:47 -0800 (PST) In-Reply-To: <18358.2182.671882.927824@kahikatea.snap.net.nz> X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:89183 Archived-At: ------=_Part_591_21882573.1203114107636 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Feb 15, 2008 4:47 PM, Nick Roberts wrote: > hi, all. sorry it's taken me a while to join this conversation. i > > adamantly want to see the pdbtrack functionality, which was integrated > > to python-mode.el, included in the python mode delivered with emacs. > > at one point it was integrated with the version of python.el that was > > supposed to be included with the release of emacs 22. i was perplexed > > and dismayed to discover, however, that somehow changed at the last > > moment, and it still hasn't been rectified. > > I never installed that patch because I was uncertain about the authorship > of the parts of python-mode.el that I was taking from. i believe that any changes to the code for pdb tracking functionality were trivial, and that my copyright assignment would be sufficient for that part of it. i can check with barry, who incorporated the stand-alone code i had written (as "pdbtrack.el") into python-mode.el > > it looks like the reason for the separate implementation of python.el > > had something to do with problems getting copyright assignments. i > > think that could be settled, and probably could help with that, but > > now we have two separate python mode implementations, and i don't know > > how to resolve the choice between them. > > > > in any case, i *do* want to see pdb tracking included in whichever. > > as the author of the feature, i should be able to authorize its use > > wherever, and am frustrated with the twisty turns of events that have > > prevented that. while my time is limited for reimplementing it, i can > > probably help with that and/or with seeing about getting license > > assignment for python-mode.el. > > I still have a local copy of the patch updated to the trunk and could > install > it now if instructed to do so. > > There appear to be two options: > > 1) Install my patch in python.el which may in reality only involve your > contribution to python-mode.el and may not require other signatures. > > 2) Replace python.el with a modified python-mode.el which would require > more signatures (Barry Warsaw, Skip Montanero?) and more work. it sounds like you have done some substantial comparison between the two implementations of python-mode, at least when you were working on the patches. can you characterize the differences between the two? i never tried python.el very far, because it lacked pdb tracking - but i've always been favorably impressed with python-mode.el, and would be expect it to offer a good basis to work from. i'm planning to contact barry and skip to see about copyright assignments - would that help? would you be willing to revisit your patches and bring them up to date, if clearance for python-mode.el became possible? > -- > Nick > http://www.inet.net.nz/~nickrob > -- ken http://myriadicity.net ------=_Part_591_21882573.1203114107636 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Feb 15, 2008 4:47 PM, Nick Roberts <nickrob@snap.net.nz> wrote:

 > hi, all.  sorry it's taken me a while to join this conversation.  i
 > adamantly want to see the pdbtrack functionality, which was integrated
 > to python-mode.el, included in the python mode delivered with emacs.
 > at one point it was integrated with the version of python.el that was
 > supposed to be included with the release of emacs 22.  i was perplexed
 > and dismayed to discover, however, that somehow changed at the last
 > moment, and it still hasn't been rectified.

I never installed that patch because I was uncertain about the authorship
of the parts of python-mode.el that I was taking from.

i believe that any changes to the code for pdb tracking functionality were trivial, and that my copyright assignment would be sufficient for that part of it.  i can check with barry, who incorporated the stand-alone code i had written (as "pdbtrack.el") into python-mode.el
 
> it looks like the reason for the separate implementation of python.el
 > had something to do with problems getting copyright assignments.  i
 > think that could be settled, and probably could help with that, but
 > now we have two separate python mode implementations, and i don't know
 > how to resolve the choice between them.
 >
 > in any case, i *do* want to see pdb tracking included in whichever.
 > as the author of the feature, i should be able to authorize its use
 > wherever, and am frustrated with the twisty turns of events that have
 > prevented that.  while my time is limited for reimplementing it, i can
 > probably help with that and/or with seeing about getting license
 > assignment for python-mode.el.

I still have a local copy of the patch updated to the trunk and could install
it now if instructed to do so.

There appear to be two options:

1) Install my patch in python.el which may in reality only involve your
  contribution to python-mode.el and may not require other signatures.

2) Replace python.el with a modified python-mode.el which would require
  more signatures (Barry Warsaw, Skip Montanero?) and more work.

it sounds like you have done some substantial comparison between the two implementations of python-mode, at least when you were working on the patches.  can you characterize the differences between the two?  i never tried python.el very far, because it lacked pdb tracking - but i've always been favorably impressed with python-mode.el, and would be expect it to offer a good basis to work from.

i'm planning to contact barry and skip to see about copyright assignments - would that help?  would you be willing to revisit your patches and bring them up to date, if clearance for python-mode.el became possible?
 
--
Nick                                           http://www.inet.net.nz/~nickrob

--
ken
http://myriadicity.net ------=_Part_591_21882573.1203114107636--