From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Christoph Scholtes Newsgroups: gmane.emacs.devel Subject: Re: Current state of python.el in the Emacs trunk Date: Tue, 29 Mar 2011 20:12:14 -0600 Message-ID: <86wrjh73wh.fsf@gmail.com> References: <4D40F55C.2040400@gmail.com> <874o85t61z.fsf@liv.ac.uk> <87y65hukcj.fsf@stupidchicken.com> <86r5b8llwc.fsf@gmail.com> <87oc66ky5s.fsf@liv.ac.uk> <861v2y9cz1.fsf@gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1301451246 19881 80.91.229.12 (30 Mar 2011 02:14:06 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 30 Mar 2011 02:14:06 +0000 (UTC) Cc: ken manheimer , Dave Love , Chong Yidong , "emacs-devel@gnu.org" To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Mar 30 04:13:55 2011 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.69) (envelope-from ) id 1Q4kuN-0004B2-TW for ged-emacs-devel@m.gmane.org; Wed, 30 Mar 2011 04:13:54 +0200 Original-Received: from localhost ([127.0.0.1]:47768 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q4kuD-0007dV-I3 for ged-emacs-devel@m.gmane.org; Tue, 29 Mar 2011 22:13:09 -0400 Original-Received: from [140.186.70.92] (port=33933 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q4ku5-0007MT-8u for emacs-devel@gnu.org; Tue, 29 Mar 2011 22:13:04 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Q4ktw-00038Z-Jj for emacs-devel@gnu.org; Tue, 29 Mar 2011 22:12:53 -0400 Original-Received: from mail-iy0-f169.google.com ([209.85.210.169]:33016) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q4ktv-000380-9q; Tue, 29 Mar 2011 22:12:51 -0400 Original-Received: by iyf13 with SMTP id 13so989603iyf.0 for ; Tue, 29 Mar 2011 19:12:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:from:to:cc:subject:in-reply-to:references :user-agent:date:message-id:mime-version:content-type; bh=lz1KBZ3ynQh16lGs9E4YMgv8lyfo6Is2wUe7a8WsSzs=; b=HMGx+yAP0he9VZ4/J1yfv3MiennuXVHwbTGt3VfxBgmWbfnQ9JwYlolvTWyiuC7WPx 2gKvtza30KfOXVSmluHMwSr7vPJ6IPV/EkqHzOrNF9ipbE6IG67fXhKgKfOVHdQWQ+pF 8/NXHuXuqy3Y6al8jwFY+JPxjjSetUIv9U1Mk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=from:to:cc:subject:in-reply-to:references:user-agent:date :message-id:mime-version:content-type; b=uPCDbpDxxFzgfnRs/UQcXq9KiUIfP0bLvirKPdO4nsvf2fEq9pOZ7hNBhto1B5yDK5 ICb6rlZ8WmyW4fdLiqMgNtBnSaoTEsgeAXObnFQZhh3kqLFIpngvUdF+cl3DXI9Y4ERJ yDTf34jZRSrV0mB61866938dGlxThRU89rAS4= Original-Received: by 10.42.161.70 with SMTP id s6mr387723icx.374.1301451169726; Tue, 29 Mar 2011 19:12:49 -0700 (PDT) Original-Received: from localhost (71-208-176-211.hlrn.qwest.net [71.208.176.211]) by mx.google.com with ESMTPS id g16sm4022226ibb.20.2011.03.29.19.12.39 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 29 Mar 2011 19:12:48 -0700 (PDT) In-Reply-To: (Stefan Monnier's message of "Tue, 29 Mar 2011 10:03:13 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (windows-nt) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 209.85.210.169 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:137885 Archived-At: Stefan Monnier writes: >> prospect. however, pdbtrack does seem to be present in the versions of >> python.el that come with Emacs 23 on the various systems i use, so i'm >> hopeful it's been adopted and will continue to be. > > There's no plan to remove it, indeed. Its global impact is a bit > problematic but that's no argument for removing the feature since it's > not a bug of the implementation but is part of the intended UI. I actually like the idea of pdbtrack quite a bit and like Stefan said, there is no plan to remove it. Fabian's implementation works really nice and also handles all corner cases well, for example the end of the script being debugged. The current pdbtrack implementation would end up in emacs2.py when stepping past the end of the script. Christoph