[Python-mode] merging python-mode.el and python.el

Dave Love fx at gnu.org
Wed Jan 28 02:01:29 CET 2009


"skip at pobox.com" <skip at pobox.com> writes:

> Based on my own personal experience I don't think you
> can lay all the blame on the folks who have contributed to python-mode.el.

Who's laying blame?  There wasn't much point in me pursuing any other
authors without an assignment for Barry's code, but it's now moot.

If you're having trouble with copyright assignments, and don't get
anywhere with the clerk, rms would probably like to know.

>     Dave> It's not clear to me what's in python-mode.el that would be useful
>     Dave> to put in python.el...
>
> A lot of people like pdbtrack.

Maybe, but it shouldn't be in Python mode, per my commentary.  Something
like that clearly shouldn't be done there and more-or-less duplicated in
N other modes with inferior interpreters.  (Actually, there is a bunch
of stuff left in python.el that shouldn't be there, and would have been
abstracted over similar modes if I'd had the chance, but at least some
of that required modifications to Emacs.)

> The python-mode project also includes bits
> Emacs Lisp and Python code to interface with Pymacs.  I believe both are
> unique to the python-mode project.

$ grep -i pymacs python-mode.el
$ grep -i pymacs python.el
(autoload 'pymacs-load "pymacs" nil t)
          (pymacs-load "bikeemacs" "brm-") ; first line of normal recipe

When I wrote python.el, as far as I could tell it had a superset of
features of the old mode which, as an experienced maintainer, I thought
should or had to be there (as opposed to things like generalized Eldoc
support, symbol completion, Capitalized Words mode, &c, and things which
violate Emacs requirements for keybindings and things).


More information about the Python-mode mailing list