emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: python.el fixes for Emacs 22


From: Barry Warsaw
Subject: Re: python.el fixes for Emacs 22
Date: Thu, 21 Feb 2008 00:09:26 -0500

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Let me just say that of all the cool Ken hacks that I've become addicted to over the years, probably the most useful to my daily life is pdbtrack. To me, it's an absolutely essential tool for a Python programmer, and it makes all my vim-loving colleagues positively drool. :) (BTW, why do all the kids love vim these days?)

On Feb 20, 2008, at 7:20 PM, Ken Manheimer wrote:

the way you've implemented it, you put the comint hook only in the
python-shell.  the thing is, python programs aren't only run from
python-shell.

In fact, I'd say almost never in my experience. I use pyshell for some simple experimentation, but 99% of the time run my programs from the shell, with a strategically placed "import pdb; pdb.set_trace()" line in the problematic code. pdbtrack makes debugging this way efficient and fun.

in fact, many python programs and servers are usually
launched as regular commands, from bash shells.  in python-mode.el,
pdb tracking is hooked into all comint shells, and i would like to see
that same thing in the python.el version.

Yes, absolutely a must.

also, i've also been talking with barry and skip, who would also be
interested in seeing the python mode versions converge.  i do see that
python-mode.el is actively maintained - it's current with the
pre-release python 3.0, and it looks like a much more complete
language mode than python.el.  would there be interest in helping to
get this convergence?  is python.el actively maintained, and if so,
would the maintainers be interested in helping consolidate the
versions?

I think Skip just recently added some support to python-mode.el for Python 3.0 syntax, and between the two of us, we do try to keep the mode up-to-date with the language. I think there will be an interesting discussion about how to, or even if we should, try to support both Python 2.6 and 3.0 in the same mode.

Skip and I are both very interested in converging the modes. It's silly and confusing to our users for there to be more than one Python mode. However, Skip and I are primarily XEmacs users so we need to work together to make sure the code is portable between the two Emacsen.

I would like to move python-mode.el out of the Python tree, and actually off of Subversion and SourceForge, and onto Bazaar and Launchpad. Would the python.el folks be up for converging on that?

- -Barry

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iQCVAwUBR70HiXEjvBPtnXfVAQLZ2AQAlftWSJicMCcsMIVDzaVi10JMiy4gPaxn
A4iwAkl2WDPaZY3wcgeWLH7ewSwwaZk6XF2b8aWzmrdndGRKhd9GxHYRmu//zApy
H/ebj3wvCKMlAOmZ52IpEnJc4tAq513y5raABWfJ0yBEQEHnlU7b+uUjk6QcFpQq
U8Yj5R33reI=
=A186
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]