Re: [Python-mode] [PDEE] CEDET integration with python-mode.el?
Hi Rocky, Sorry about the late reply. On Sun, Mar 21, 2010 at 3:52 AM, Rocky Bernstein rocky.bernst...@gmail.com wrote: Comments in line. On Sat, Mar 20, 2010 at 6:35 PM, Yaroslav Halchenko li...@onerussian.com wrote: On Sat, 20 Mar 2010, Rohan Nicholls wrote: Ipython + python-mode + python-ropemacs + pylint + flymake + outline ... I have also used such a setup, and it has a lot to offer, but I found that it really dies on you when you work with big projects. I think ... I had similar slowdown/cpu_intensive experience with some versions of pylint and more or less large projects but then it somehow became sane again (didn't check if any recent version changelog had any performance/dependecy_tracking improvements mentioned) emacs frontend to rpdb (command line version of the winpdb debugger), which seems to handle threading as well if not better than anyone else. Pdb falls down horribly when dealing with multi-threaded applications such as a wx-python or zope app. what about pydb (or even may be a new rewrite pydbgr ?) I bet Rocky (their author) who is also an emacs user might like to join the forces to provide adequate glue? Of course, I'm happy to work with folks who are interested in using pydbgr and ensuring it plays nice with other tools. Strategically I'd like to see it and other debuggers of this ilk use DBGp, the remote debugging protocol. See http://xdebug.org/docs-dbgp.php. Right now though pydbgr has remote debugging support using a home-grown protocol based on the Ruby debugger ruby-debug. And by the way, both pydb and pydbgr do support working with threads. As for emacs and debugger integration, see the emacs-dbgr project on github http://github.com/rocky/emacs-dbgr. It has lots of rough edges but personally I use it all the time. Generally though I use it with debuggers such as for Ruby, POSIX shells and gdb since I don't do much Python coding. I have been looking at this, but the docs seem a little scarce and I have not yet had time to start looking through the code. but man, you have a lot of tests. Nice work. emacs-dbgr definitely is a much better foundation to work with on the Emacs side for debuggers than gud.el. It makes better use of Emacs Lisp and Emacs built in capabilities. For example it uses marks to store locations in the source and process buffers; it uses a ring to store history locations and buffer-local structs to store debugger information. Right now emacs-dbgr only supports for pydbgr with regards to Python, but adding other debuggers such as pdb, pydb, or rpdb is pretty easy. If someone is interested in that let me know. Well I would be, as zope2 which is what plone runs on only supports python 2.4 which rules out pydbgr (as much as I would like to use it), so I am reading the docs for pydb at the moment, and am happy to start hacking it into the emacs-dbgr project. Really nice idea by the way, and very needed, there are so many debuggers that run through emacs, and gud is indeed very static compiler oriented. The gating factor on all of this development work is that the lack of interest in the community. Personally I don't have need to use Python right now, and historically ipython and Python folks haven't been much interested in pydb let alone pydbgr. But to be fair, I'm not sure that historically there has been all that much interest in pdb either. This is an unfortunate problem. The winpdb developer has brought this up on his blogs. :) Btw. is there a mailing list or something for emacs-dbgr? Thanks for all this work, it is really great, although I am curious as to why, if you don't use python much yourself, you are writing an improved debugger for it. Rohan ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
Re: [Python-mode] [PDEE] CEDET integration with python-mode.el?
On Sat, Mar 20, 2010 at 3:22 AM, Yaroslav Halchenko li...@onerussian.com wrote: On Tue, 16 Mar 2010, Tom Roche wrote: It Seems To Me (quite possibly naively) that the best/easiest way to get smarter completion particularly, and several more services besides, is to use CEDET or may be (citing my post earlier in this list): Ipython + python-mode + python-ropemacs + pylint + flymake + outline make emacs very well featured for Python mode development (completions, documentation lookup, jump to definition, etc). You might look into my messy .emacs setup [1] or excerpt from it, which I placed into pymvpa project [2], on how to make such combination work nicely. I have also used such a setup, and it has a lot to offer, but I found that it really dies on you when you work with big projects. I think it is the rope library, because working on a zope project or the large code base I was working on at my last job, and getting a completion or saving a file would make everything really, really slow, or worse, send rope into a complete tailspin. I would love to see python and cedet come together, as there is so much functionality out of the box with cedet, while with rope etc. the project browsing is seriously lacking, as was semantic code completion. As fabulous as ipython is, it only understands what it has processed, and has problems (not its fault, this is something that lies deep in the python interpretor itself) updating the object environment, so updating functions, methods and classes with ipython does not necessarily update the current objects, in fact more often than not doesn't. I would also like to add; there is no really good python development tools, and if pdee came about combining the cedet functionality with good debugging integration, it would be ahead of current python ides (IMHO). About the debugging, I was thinking that maybe creating an emacs frontend to rpdb (command line version of the winpdb debugger), which seems to handle threading as well if not better than anyone else. Pdb falls down horribly when dealing with multi-threaded applications such as a wx-python or zope app. One thing that is really nice about rope, is that it does handle refactoring really well, in fact it had a lot of features that wingide could not match (I have used both), but maybe cedet has these facilities. Anyway, that was my thinking. Do I have the slightest clue where to start to make this happen? Nope. But I am still working in python, and at the moment with zope, so I need to find or help build a solution, and if it uses emacs as its frontend so much the better. Thanks, Rohan ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
Re: [Python-mode] triple-quoted-string bug fixed
Damn, that was fast. Thanks. On Thu, Sep 10, 2009 at 1:54 PM, Andreas Roehler andreas.roeh...@online.de wrote: Hi Barry, diff attached against latest python-mode.el solves bug 328790, the triple string bug for me - checked with X- and GNU Emacs. Took some stuff from python.el, thanks towards its excellent author BTW. Did create a branch for it. Log now reads revno: 352 committer: Andreas Roehler andreas.roeh...@online.de branch nick: python-mode timestamp: Thu 2009-09-10 13:30:24 +0200 message: --fixes=lp:328790 Should I try bzr push lp:~a-roehler/python-mode/triple-quoted-string-bug-328790.el ? Cheers Andreas ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
[Python-mode] looking for a discussion of things python(-mode) ish
Hi all, I was looking for information about ptyhon.el and ipython.el and have started making ipython work with python.el, when I stumbled on the consolidation attempt of the two modes. I checked out the python-mode launchpad project, and am now sending an email. Do I need to sign up to the python mailing list to see any discussions? Or does this email get me added to some secret list? ;) I am very interested in getting everything under one roof, although the discussion I read in January seems to indicate that this will never be. Just to sum up reasons that I had started using python.el - python-mode had shown no sign of life for about 5 years - The killer was the triple quote bug. I was horribly stung by this, and at that point tossed python-mode even though the integration with ipython.el is hard to beat. - I am an emacs user, having given up on xemacs a couple of years ago, and it shows no sign of improving, so emacs specificity is not a problem for me, in fact it is a plus, as the various incompatible bits of the two systems do not start clogging up the code. So my questions are: - Is the triple quote threat solved in python-mode (because it is in python.el) - It seems development has started up again, would this be correct, and is there a list of things to fix somewhere? Also has Beverley Eyre compiled that list of features she mentioned back in January? Please reply to me directly, esp. about a python-mode mailing list, so I can sign up. Thanks in advance for info. :) Rohan ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
