From barry at python.org Fri May 1 21:46:41 2009 From: barry at python.org (Barry Warsaw) Date: Fri, 1 May 2009 15:46:41 -0400 Subject: [Python-mode] pdbtrack In-Reply-To: <49FA0514.4020107@online.de> References: <49FA0514.4020107@online.de> Message-ID: <8E7C25FA-091C-43B4-BE6B-6BD609089EF4@python.org> On Apr 30, 2009, at 4:07 PM, Andreas Roehler wrote: > I'll send you two screenshots offlist. Please feel > free to forward them to interested persons, just didn't > want to publish my path at the list. > > 20090428_pdbtrack3.png displays pdbtrack opened second > windows, cursor displayed at line 4 "import" > > With 20090428_pdbtrack4.png you see shell-output > from line 8, but cursor in second window still is at line 4. > > Always get "Traceback cue not found" > > Cause seems var `py-pdbtrack-stack-entry-regexp'. > > That doesn't happen, if pdb.set_trace() is inside the > python-file. > > Did someone else remark this? Hi Andreas, I haven't heard this one before, but perhaps it's because of the ipython prompt? I think pdbtrack expects (by default) the standard (pdb) prompt. -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 304 bytes Desc: This is a digitally signed message part URL: From andreas.roehler at online.de Fri May 1 22:50:09 2009 From: andreas.roehler at online.de (Andreas Roehler) Date: Fri, 01 May 2009 22:50:09 +0200 Subject: [Python-mode] pdbtrack In-Reply-To: <8E7C25FA-091C-43B4-BE6B-6BD609089EF4@python.org> References: <49FA0514.4020107@online.de> <8E7C25FA-091C-43B4-BE6B-6BD609089EF4@python.org> Message-ID: <49FB6081.7050409@online.de> Barry Warsaw wrote: > On Apr 30, 2009, at 4:07 PM, Andreas Roehler wrote: > >> I'll send you two screenshots offlist. Please feel >> free to forward them to interested persons, just didn't >> want to publish my path at the list. >> >> 20090428_pdbtrack3.png displays pdbtrack opened second >> windows, cursor displayed at line 4 "import" >> >> With 20090428_pdbtrack4.png you see shell-output >> from line 8, but cursor in second window still is at line 4. >> >> Always get "Traceback cue not found" >> >> Cause seems var `py-pdbtrack-stack-entry-regexp'. >> >> That doesn't happen, if pdb.set_trace() is inside the >> python-file. >> >> Did someone else remark this? > > Hi Andreas, > > I haven't heard this one before, but perhaps it's because of the ipython > prompt? Maybe. As shows message in first screenshot #3, pdbtrack indicates line 4 correctly. Its not brocken completely. Its a question of regexp, which doesn't recognise/accept the result, delivered by `block'. Already tried to change the regexp or even simply eliminate that checking step, but not found a solution. Hhm. Could you give me an example, how you run script activating pdbtrace, reaching the standard (pdb) prompt from Emacs? Only get it from shell. Thanks Andreas I think pdbtrack expects (by default) the standard (pdb) prompt. > > -Barry > From barry at python.org Fri May 1 22:54:51 2009 From: barry at python.org (Barry Warsaw) Date: Fri, 1 May 2009 16:54:51 -0400 Subject: [Python-mode] pdbtrack In-Reply-To: <49FB6081.7050409@online.de> References: <49FA0514.4020107@online.de> <8E7C25FA-091C-43B4-BE6B-6BD609089EF4@python.org> <49FB6081.7050409@online.de> Message-ID: <565F38A3-F0C9-42B7-808D-E6CF6652F5C0@python.org> On May 1, 2009, at 4:50 PM, Andreas Roehler wrote: > Hhm. Could you give me an example, how you run script activating > pdbtrace, reaching > the standard (pdb) prompt from Emacs? I almost always just add the following line to the source code at the point I want to start debugging: import pdb; pdb.set_trace() Then I fire up my application from the shell. When that line gets it, Python breaks and pdbtrack starts up. It's worked pretty much that way for me since forever. -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 304 bytes Desc: This is a digitally signed message part URL: From ken.manheimer at gmail.com Fri May 1 23:28:08 2009 From: ken.manheimer at gmail.com (ken manheimer) Date: Fri, 1 May 2009 17:28:08 -0400 Subject: [Python-mode] pdbtrack In-Reply-To: <49FB6081.7050409@online.de> References: <49FA0514.4020107@online.de> <8E7C25FA-091C-43B4-BE6B-6BD609089EF4@python.org> <49FB6081.7050409@online.de> Message-ID: <2cd46e7f0905011428x67ad2877rc4ab5d69fec3f51a@mail.gmail.com> On Fri, May 1, 2009 at 4:50 PM, Andreas Roehler wrote: > Barry Warsaw wrote: > > On Apr 30, 2009, at 4:07 PM, Andreas Roehler wrote: > > > >> I'll send you two screenshots offlist. Please feel > >> free to forward them to interested persons, just didn't > >> want to publish my path at the list. > >> > >> 20090428_pdbtrack3.png displays pdbtrack opened second > >> windows, cursor displayed at line 4 "import" > >> > >> With 20090428_pdbtrack4.png you see shell-output > >> from line 8, but cursor in second window still is at line 4. > >> > >> Always get "Traceback cue not found" > >> > >> Cause seems var `py-pdbtrack-stack-entry-regexp'. > >> > >> That doesn't happen, if pdb.set_trace() is inside the > >> python-file. > >> > >> Did someone else remark this? > > > > Hi Andreas, > > > > I haven't heard this one before, but perhaps it's because of the ipython > > prompt? > > Maybe. As shows message in first screenshot #3, pdbtrack indicates line 4 > correctly. > Its not brocken completely. > i'm having some difficulties tracking your descriptions of the situation, andreas, but i think you (and barry) are right that the problem is failure to recognize, rather than pdbtrack not being activated (as you seemed to initially be suggesting). > Its a question of regexp, which doesn't recognise/accept the result, > delivered by `block'. > i don't understand what you mean by "delivered by 'block'" > Already tried to change the regexp or even simply eliminate that checking > step, but not > found a solution. > the match may be necessary to parse the traceback, and for other reasons. Hhm. Could you give me an example, how you run script activating pdbtrace, > reaching > the standard (pdb) prompt from Emacs? > what do you mean by "reaching the standard (pdb) prompt from Emacs"?? perhaps you're talking about the python interaction buffer that python-mode provides? i believe, but am not certain, that pdbtrack watches the output in any comint buffer, including the python interaction buffer. i can check this kind of thing, but need to understand better what you're saying before investigating. Only get it from shell. > one thing i can suggest that you do is copy the text from the emacs buffer that pdbtrack should recognize but doesn't, and send that excerpt to us. i know that's in the pictures, but it's easier for you to send us the text than it is for us to type it accurately from the pictures.-) preferably you would also send an excerpt that is similar but is successfuly recognized. i will try to find time to examine it, and see if i can identify what is happening and what should be happening... -- ken http://myriadicity.net > Thanks > > Andreas > > > I think pdbtrack expects (by default) the standard (pdb) prompt. > > > > -Barry > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ken.manheimer at gmail.com Sat May 2 00:50:39 2009 From: ken.manheimer at gmail.com (ken manheimer) Date: Fri, 1 May 2009 18:50:39 -0400 Subject: [Python-mode] pdbtrack In-Reply-To: <2cd46e7f0905011428x67ad2877rc4ab5d69fec3f51a@mail.gmail.com> References: <49FA0514.4020107@online.de> <8E7C25FA-091C-43B4-BE6B-6BD609089EF4@python.org> <49FB6081.7050409@online.de> <2cd46e7f0905011428x67ad2877rc4ab5d69fec3f51a@mail.gmail.com> Message-ID: <2cd46e7f0905011550v6b891fe7i83f20e25ab44d54a@mail.gmail.com> looking at this a little bit more closely, it's surprising to me not that it fails for you, but that it works at all. have you made any changes to the py-pdbtrack-input-prompt variable (aka 'python-pdbtrack-input-prompt' in recent versions of python.el)? as the docstring for py-pdbtrack-track-stack-file states, "We depend on the pdb input prompt matching `py-pdbtrack-input-prompt' at the beginning of the line." the default setting simply should not match the "ipydb> " that your photos are showing. ? sorry if i'm missing something obvious - i'm trying to get context here, with not quite enough time to pay full attention... -- ken http://myriadicity.net On Fri, May 1, 2009 at 5:28 PM, ken manheimer wrote: > On Fri, May 1, 2009 at 4:50 PM, Andreas Roehler > wrote: > >> Barry Warsaw wrote: >> > On Apr 30, 2009, at 4:07 PM, Andreas Roehler wrote: >> > >> >> I'll send you two screenshots offlist. Please feel >> >> free to forward them to interested persons, just didn't >> >> want to publish my path at the list. >> >> >> >> 20090428_pdbtrack3.png displays pdbtrack opened second >> >> windows, cursor displayed at line 4 "import" >> >> >> >> With 20090428_pdbtrack4.png you see shell-output >> >> from line 8, but cursor in second window still is at line 4. >> >> >> >> Always get "Traceback cue not found" >> >> >> >> Cause seems var `py-pdbtrack-stack-entry-regexp'. >> >> >> >> That doesn't happen, if pdb.set_trace() is inside the >> >> python-file. >> >> >> >> Did someone else remark this? >> > >> > Hi Andreas, >> > >> > I haven't heard this one before, but perhaps it's because of the ipython >> > prompt? >> >> Maybe. As shows message in first screenshot #3, pdbtrack indicates line 4 >> correctly. >> Its not brocken completely. >> > > i'm having some difficulties tracking your descriptions of the situation, > andreas, but i think you (and barry) are right that the problem is failure > to recognize, rather than pdbtrack not being activated (as you seemed to > initially be suggesting). > > >> Its a question of regexp, which doesn't recognise/accept the result, >> delivered by `block'. >> > > i don't understand what you mean by "delivered by 'block'" > > >> Already tried to change the regexp or even simply eliminate that checking >> step, but not >> found a solution. >> > > the match may be necessary to parse the traceback, and for other reasons. > > Hhm. Could you give me an example, how you run script activating pdbtrace, >> reaching >> the standard (pdb) prompt from Emacs? >> > > what do you mean by "reaching the standard (pdb) prompt from Emacs"?? > perhaps you're talking about the python interaction buffer that python-mode > provides? i believe, but am not certain, that pdbtrack watches the output > in any comint buffer, including the python interaction buffer. i can check > this kind of thing, but need to understand better what you're saying before > investigating. > > Only get it from shell. >> > > one thing i can suggest that you do is copy the text from the emacs buffer > that pdbtrack should recognize but doesn't, and send that excerpt to us. i > know that's in the pictures, but it's easier for you to send us the text > than it is for us to type it accurately from the pictures.-) preferably you > would also send an excerpt that is similar but is successfuly recognized. > > i will try to find time to examine it, and see if i can identify what is > happening and what should be happening... > -- > ken > http://myriadicity.net > > >> Thanks >> >> Andreas >> >> >> I think pdbtrack expects (by default) the standard (pdb) prompt. >> > >> > -Barry >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andreas.roehler at online.de Sat May 2 08:58:23 2009 From: andreas.roehler at online.de (Andreas Roehler) Date: Sat, 02 May 2009 08:58:23 +0200 Subject: [Python-mode] pdbtrack In-Reply-To: <2cd46e7f0905011550v6b891fe7i83f20e25ab44d54a@mail.gmail.com> References: <49FA0514.4020107@online.de> <8E7C25FA-091C-43B4-BE6B-6BD609089EF4@python.org> <49FB6081.7050409@online.de> <2cd46e7f0905011428x67ad2877rc4ab5d69fec3f51a@mail.gmail.com> <2cd46e7f0905011550v6b891fe7i83f20e25ab44d54a@mail.gmail.com> Message-ID: <49FBEF0F.9060906@online.de> ken manheimer wrote: > looking at this a little bit more closely, it's surprising to me not > that it fails for you, but that it works at all. Hi Ken, thats the point probably. Originally question was: must we change the source-code in order to make pdbtrack working, must we put a pdb.set_trace() into it? Tried to avoid that and watched results coming from pdb also without that. While executing, results are delivered to function py-pdbtrack-get-source-buffer (block) line 1444 of my python-mode.el Then (string-match py-pdbtrack-stack-entry-regexp block) decides to accept result or not. Played a little bit with py-pdbtrack-stack-entry-regexp:. ;; pdbtrack constants (defconst py-pdbtrack-stack-entry-regexp ; "^> \\([^(]+\\)(\\([0-9]+\\))\\([?a-zA-Z0-9_]+\\)()" ;; "^> \\(.*\\)(\\([0-9]+\\))\\([?a-zA-Z0-9_]+\\)()" "> \\(.*\\)(\\([0-9]+\\))\\(.*\\)()" ;; "^ \\(.*\\)" "Regular expression pdbtrack uses to find a stack trace entry.") Andreas have you made any > changes to the py-pdbtrack-input-prompt variable (aka > 'python-pdbtrack-input-prompt' in recent versions of python.el)? > > as the docstring for py-pdbtrack-track-stack-file states, "We depend on > the pdb input prompt matching `py-pdbtrack-input-prompt' at the > beginning of the line." the default setting simply should not match the > "ipydb> " that your photos are showing. ? > > sorry if i'm missing something obvious - i'm trying to get context here, > with not quite enough time to pay full attention... > -- > ken > http://myriadicity.net > > On Fri, May 1, 2009 at 5:28 PM, ken manheimer > wrote: > > On Fri, May 1, 2009 at 4:50 PM, Andreas Roehler > > wrote: > > Barry Warsaw wrote: > > On Apr 30, 2009, at 4:07 PM, Andreas Roehler wrote: > > > >> I'll send you two screenshots offlist. Please feel > >> free to forward them to interested persons, just didn't > >> want to publish my path at the list. > >> > >> 20090428_pdbtrack3.png displays pdbtrack opened second > >> windows, cursor displayed at line 4 "import" > >> > >> With 20090428_pdbtrack4.png you see shell-output > >> from line 8, but cursor in second window still is at line 4. > >> > >> Always get "Traceback cue not found" > >> > >> Cause seems var `py-pdbtrack-stack-entry-regexp'. > >> > >> That doesn't happen, if pdb.set_trace() is inside the > >> python-file. > >> > >> Did someone else remark this? > > > > Hi Andreas, > > > > I haven't heard this one before, but perhaps it's because of > the ipython > > prompt? > > Maybe. As shows message in first screenshot #3, pdbtrack > indicates line 4 correctly. > Its not brocken completely. > > > i'm having some difficulties tracking your descriptions of the > situation, andreas, but i think you (and barry) are right that the > problem is failure to recognize, rather than pdbtrack not being > activated (as you seemed to initially be suggesting). > > > Its a question of regexp, which doesn't recognise/accept the > result, delivered by `block'. > > > i don't understand what you mean by "delivered by 'block'" > > > Already tried to change the regexp or even simply eliminate that > checking step, but not > found a solution. > > > the match may be necessary to parse the traceback, and for other > reasons. > > Hhm. Could you give me an example, how you run script activating > pdbtrace, reaching > the standard (pdb) prompt from Emacs? > > > what do you mean by "reaching the standard (pdb) prompt from > Emacs"?? perhaps you're talking about the python interaction buffer > that python-mode provides? i believe, but am not certain, that > pdbtrack watches the output in any comint buffer, including the > python interaction buffer. i can check this kind of thing, but need > to understand better what you're saying before investigating. > > Only get it from shell. > > > one thing i can suggest that you do is copy the text from the emacs > buffer that pdbtrack should recognize but doesn't, and send that > excerpt to us. i know that's in the pictures, but it's easier for > you to send us the text than it is for us to type it accurately from > the pictures.-) preferably you would also send an excerpt that is > similar but is successfuly recognized. > > i will try to find time to examine it, and see if i can identify > what is happening and what should be happening... > -- > ken > http://myriadicity.net > > > Thanks > > Andreas > > > I think pdbtrack expects (by default) the standard (pdb) prompt. > > > > -Barry > From andreas.roehler at easy-emacs.de Sun May 3 09:49:15 2009 From: andreas.roehler at easy-emacs.de (=?ISO-8859-1?Q?Andreas_R=F6hler?=) Date: Sun, 03 May 2009 09:49:15 +0200 Subject: [Python-mode] [Fwd: Re: python setup ?] Message-ID: <49FD4C7B.5070908@easy-emacs.de> -------------- next part -------------- An embedded message was scrubbed... From: bbbscarter at gmail.com Subject: Re: python setup ? Date: Fri, 1 May 2009 14:35:07 -0700 (PDT) Size: 3862 URL: From andreas.roehler at easy-emacs.de Mon May 4 21:59:19 2009 From: andreas.roehler at easy-emacs.de (=?UTF-8?B?QW5kcmVhcyBSw7ZobGVy?=) Date: Mon, 04 May 2009 21:59:19 +0200 Subject: [Python-mode] python setup ? In-Reply-To: <49ff1e8a.0407560a.7f38.137e@mx.google.com> References: <200904280634.n3S6YctW009278@zogzog.maillard.mobi> <49F95274.4000801@easy-emacs.de> <49ff1e8a.0407560a.7f38.137e@mx.google.com> Message-ID: <49FF4917.3050502@easy-emacs.de> Richard Riley wrote: > Barry Warsaw writes: > > >> On Apr 30, 2009, at 3:25 AM, Andreas R?hler wrote: >> >> >>> With python-mode.el, people may have good reasons, to >>> use it as it is - and me to leave it as it is. Thats >>> fine with bazaar and other DVCs, we can do that. My >>> branch doesn't hamper the origin and any further branch >>> will not. Its just freedom to try and see. >>> >> This is true, and experimentation a good thing in the short term. In >> the long term though, a proliferation of branches just confuses people >> because no one's sure which is the official branch. Our lives are >> more difficult too because of the python-mode.el/python.el split. >> >> So I encourage you to experiment and get user feedback. Old-timers >> (and remember, python-mode.el's been in widespread use for 15 years) >> will be wedded to their muscle memory, but if you introduce a user- >> visible change that people like, they can be made configurable with >> defaults providing the old behavior. Then it will be possible to >> merge your changes back into the official branch. If you modularize >> your changes, then the less controversial ones can get merged in sooner. >> >> -Barry >> >> >> > > > IMO any new "obviously useful" features should be enabled by > default. Old Timers should have no problem reverting to older > configurations via settings. A point which generates much contention I > know. As it is, Python set up is/was a minefield. I have a reasonable > set up here fwiw, > Yes, you have. Used it month ago, thanks BTW. Beside the question is still, how the user may get everything needed installed with one action. Several possibilities exist: we could make a tarball emacs-python. Too we should let the user decide, what features to use: ipython or not, pdbtrack or pydb, which completion, refactoring, which checks and tests etc. > This includes pysmell completions for hippie expand and company-mode. > > http://richardriley.net/projects/emacs/dotprogramming#sec-1.3 > > > > From rileyrgdev at googlemail.com Mon May 4 18:57:46 2009 From: rileyrgdev at googlemail.com (Richard Riley) Date: Mon, 04 May 2009 18:57:46 +0200 Subject: [Python-mode] python setup ? In-Reply-To: (Barry Warsaw's message of "Thu, 30 Apr 2009 09:24:46 -0400") References: <200904280634.n3S6YctW009278@zogzog.maillard.mobi> <49F95274.4000801@easy-emacs.de> Message-ID: <49ff1e8a.0407560a.7f38.137e@mx.google.com> Barry Warsaw writes: > On Apr 30, 2009, at 3:25 AM, Andreas R?hler wrote: > >> With python-mode.el, people may have good reasons, to >> use it as it is - and me to leave it as it is. Thats >> fine with bazaar and other DVCs, we can do that. My >> branch doesn't hamper the origin and any further branch >> will not. Its just freedom to try and see. > > This is true, and experimentation a good thing in the short term. In > the long term though, a proliferation of branches just confuses people > because no one's sure which is the official branch. Our lives are > more difficult too because of the python-mode.el/python.el split. > > So I encourage you to experiment and get user feedback. Old-timers > (and remember, python-mode.el's been in widespread use for 15 years) > will be wedded to their muscle memory, but if you introduce a user- > visible change that people like, they can be made configurable with > defaults providing the old behavior. Then it will be possible to > merge your changes back into the official branch. If you modularize > your changes, then the less controversial ones can get merged in sooner. > > -Barry > > IMO any new "obviously useful" features should be enabled by default. Old Timers should have no problem reverting to older configurations via settings. A point which generates much contention I know. As it is, Python set up is/was a minefield. I have a reasonable set up here fwiw, This includes pysmell completions for hippie expand and company-mode. http://richardriley.net/projects/emacs/dotprogramming#sec-1.3 From barry at python.org Tue May 5 16:04:41 2009 From: barry at python.org (Barry Warsaw) Date: Tue, 5 May 2009 10:04:41 -0400 Subject: [Python-mode] python setup ? In-Reply-To: <49FF4917.3050502@easy-emacs.de> References: <200904280634.n3S6YctW009278@zogzog.maillard.mobi> <49F95274.4000801@easy-emacs.de> <49ff1e8a.0407560a.7f38.137e@mx.google.com> <49FF4917.3050502@easy-emacs.de> Message-ID: <78930BCB-1F63-4902-BE7B-3C0636DB9E88@python.org> On May 4, 2009, at 3:59 PM, Andreas R?hler wrote: >> IMO any new "obviously useful" features should be enabled by >> default. Old Timers should have no problem reverting to older >> configurations via settings. A point which generates much >> contention I >> know. As it is, Python set up is/was a minefield. I have a reasonable >> set up here fwiw, >> > > Yes, you have. Used it month ago, thanks BTW. > Beside the question is still, how the user may get everything needed > installed with one action. > Several possibilities exist: we could make a tarball emacs-python. If you have permission of the authors of the other packages, I have no problem distributing them in our branch, or making a tarball of them available from the Launchpad download page. It's up to them though. I tend not to use those other packages and just grab python-mode.el from its bzr branch. > Too we should let the user decide, what features to use: ipython or > not, > pdbtrack or pydb, which > completion, refactoring, which checks and tests etc. Sure. I would tend to be more conservative in the default settings, so as not to surprise people, but that's just me. :) -Barryu -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 304 bytes Desc: This is a digitally signed message part URL: From andreas.roehler at easy-emacs.de Tue May 5 17:09:10 2009 From: andreas.roehler at easy-emacs.de (=?ISO-8859-1?Q?Andreas_R=F6hler?=) Date: Tue, 05 May 2009 17:09:10 +0200 Subject: [Python-mode] python setup ? In-Reply-To: <78930BCB-1F63-4902-BE7B-3C0636DB9E88@python.org> References: <200904280634.n3S6YctW009278@zogzog.maillard.mobi> <49F95274.4000801@easy-emacs.de> <49ff1e8a.0407560a.7f38.137e@mx.google.com> <49FF4917.3050502@easy-emacs.de> <78930BCB-1F63-4902-BE7B-3C0636DB9E88@python.org> Message-ID: <4A005696.2070106@easy-emacs.de> Barry Warsaw wrote: > On May 4, 2009, at 3:59 PM, Andreas R?hler wrote: > >>> IMO any new "obviously useful" features should be enabled by >>> default. Old Timers should have no problem reverting to older >>> configurations via settings. A point which generates much contention I >>> know. As it is, Python set up is/was a minefield. I have a reasonable >>> set up here fwiw, >>> >> >> Yes, you have. Used it month ago, thanks BTW. >> Beside the question is still, how the user may get everything needed >> installed with one action. >> Several possibilities exist: we could make a tarball emacs-python. > > If you have permission of the authors of the other packages, I have no > problem distributing them in our branch, or making a tarball of them > available from the Launchpad download page. It's up to them though. Thanks a lot. I'll care for that. It will be great, if emacs-python-folks may use this facility for emacs-python-things independently from existing files, thus python-mode understood in a broader sense, rather python-mode(s). > I tend not to use those other packages and just grab python-mode.el > from its bzr branch. > >> Too we should let the user decide, what features to use: ipython or not, >> pdbtrack or pydb, which >> completion, refactoring, which checks and tests etc. > > Sure. I would tend to be more conservative in the default settings, > so as not to surprise people, but that's just me. :) > That's wise. With releases, users shouldn't be bothered with all the developing stuff. Also we could consider bundles for beginners as well as for powered-through master-pythons. :) Andreas > -Barryu > From andreas.roehler at easy-emacs.de Fri May 8 11:16:35 2009 From: andreas.roehler at easy-emacs.de (=?UTF-8?B?QW5kcmVhcyBSw7ZobGVy?=) Date: Fri, 08 May 2009 11:16:35 +0200 Subject: [Python-mode] python setup ? In-Reply-To: <49f5b71c.0305560a.6147.25ed@mx.google.com> References: <49F59516.2080901@easy-emacs.de> <49f5b71c.0305560a.6147.25ed@mx.google.com> Message-ID: <4A03F873.8030600@easy-emacs.de> Richard Riley wrote: > hi Andreas, > > but can one list breakpoints in pydb? Cant see how. > > r. > > info breakpoints http://bashdb.sourceforge.net/pydb/pydb/lib/subsubsection-info.html Gr??e Andreas From andreas.roehler at online.de Thu May 28 13:09:18 2009 From: andreas.roehler at online.de (Andreas Roehler) Date: Thu, 28 May 2009 13:09:18 +0200 Subject: [Python-mode] What text editor is everyone using for Python In-Reply-To: References: <4a1d628f$0$6471$426a74cc@news.free.fr> Message-ID: <4A1E70DE.4080407@online.de> Rhodri James wrote: > On Wed, 27 May 2009 16:56:12 +0100, Bruno Desthuilliers > wrote: > >> Rhodri James a ?crit : >>> On Tue, 26 May 2009 14:22:29 +0100, Roy Smith wrote: >>> >>>> My pet peeve is syntax-aware editors which get things wrong. For >>>> example, >>>> the version of emacs I'm using now doesn't parse this properly: >>>> >>>> '''A triple-quoted string. Some editors won't get this right''' >>>> >>>> The solution is to change the outer quotes to double-quotes, but it >>>> annoys me when I have to change my code to appease a tool. >>> It's the separate python-mode that gets this (and much else) wrong. >>> The Python mode that Ubuntu packages with emacs 22.2.1 works just >>> fine. >> >> On this point, indeed. But it also lacks almost every nice feature of >> the One True python-mode (or at least did last time I had to update >> this ... ubuntu box at work). > > That rather depends on your definition of "nice". The only feature of > python-mode.el that I miss in python.el is the ability to run pylint from > the menu, Thanks mentioning it, I'll cc this to python-mode at python.org and I'll get over that. The feature that caused me to uninstall > python-mode.el was its bloody-minded determination to regard '_' as a word > character, something which caused me more typing that it ever saved. > Its just one line to comment in python-mode.el, like this: ;; (modify-syntax-entry ?\_ "w" py-mode-syntax-table) From barry at python.org Fri May 29 23:10:43 2009 From: barry at python.org (Barry Warsaw) Date: Fri, 29 May 2009 17:10:43 -0400 Subject: [Python-mode] What text editor is everyone using for Python In-Reply-To: <4A1E70DE.4080407@online.de> References: <4a1d628f$0$6471$426a74cc@news.free.fr> <4A1E70DE.4080407@online.de> Message-ID: On May 28, 2009, at 7:09 AM, Andreas Roehler wrote: >> python-mode.el was its bloody-minded determination to regard '_' as >> a word >> character, something which caused me more typing that it ever saved. >> > > Its just one line to comment in python-mode.el, like this: > > ;; (modify-syntax-entry ?\_ "w" py-mode-syntax-table) This one is ancient and I remember that Guido and I talked about this for a long time before settling on the behavior. -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 832 bytes Desc: This is a digitally signed message part URL: From celoserpa at gmail.com Sat May 30 01:21:58 2009 From: celoserpa at gmail.com (Marcelo de Moraes Serpa) Date: Fri, 29 May 2009 18:21:58 -0500 Subject: [Python-mode] What text editor is everyone using for Python In-Reply-To: References: <4a1d628f$0$6471$426a74cc@news.free.fr> <4A1E70DE.4080407@online.de> Message-ID: <1e5bcefd0905291621v389d2f27y5c66e05f293c5089@mail.gmail.com> stop! Use the editor you are comfortable with. No flame wars please, even though Emacs is the way to enlightenment :) On Fri, May 29, 2009 at 4:10 PM, Barry Warsaw wrote: > On May 28, 2009, at 7:09 AM, Andreas Roehler wrote: > > python-mode.el was its bloody-minded determination to regard '_' as a word >>> character, something which caused me more typing that it ever saved. >>> >>> >> Its just one line to comment in python-mode.el, like this: >> >> ;; (modify-syntax-entry ?\_ "w" py-mode-syntax-table) >> > > This one is ancient and I remember that Guido and I talked about this for a > long time before settling on the behavior. > > -Barry > > > -- > http://mail.python.org/mailman/listinfo/python-list > > -------------- next part -------------- An HTML attachment was scrubbed... URL: