-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Feb 1, 2009, at 1:26 PM, Dave Love wrote:
Doubtless, but Emacs isn't just for Python programmers, and surely
modes
should be consistent.
That's pretty much a universal design decision across all of software,
isn't it? python.el takes one approach, python-mode.el takes a
different one. I've been a X/Emacs user for probably close to 25
years and python-mode.el does not feel unnatural to me, even if it has
some unorthodox coding conventions.
I rely (modulo a few historical things which
should be fixed) on the same conventions if I'm hacking Python as,
say,
Fortran, sh, or Lisp. In fact, part of the idea of the new mode was
to
figure out what more to abstract over similar modes.
Sure, all valid approaches, although there's an important difference
in aims between python.el and python-mode.el. The former only cares
about Emacs compatibility. The latter cares about both Emacs and
XEmacs compatibility. In many cases the abstraction are different
enough as to make refactoring a challenge.
If people don't like the conventions or want things which break other
code, they can customize and distribute the customizations, of course.
(Custom theme support may help.) I'd hope they'd try to understand
the
general conventions, though, and not cause confusion over them.
Sure, but there's another difference. python-mode.el has been around
for a very long time and its users for the most part like the way it
works. As someone who would likely begin to curse his own fingers, I
don't think we should break that backwards compatibility in python-
mode.el.
Let's agree that everyone involved have the right intention to
improve
the situation,
I don't doubt your intentions -- sorry if it seems otherwise. It's a
different matter for someone else if they don't respect the FSF's
copyright, for instance, and that's presumably mutual.
Of course.
I certainly appreciate the arguments that Andreas and Beverley make as
to copyright. I have my own opinions on that subject both as a FLOSS
developer and musician. But this isn't an effective forum for
changing either the FSF's stance, nor US or international law on the
matter, so I believe we must adapt to the regime under which we live,
and take the fight to the forums where such change can actually be
affected.
I still propose we GPLv3 python-mode.el. Thus if we cannot merge, we
will simply continue to develop python-mode.el separately, educate
users as to the differences, and let them decide which they prefer.
With a GPLv3 python-mode.el we can all borrow from each other.
Fine. That solves the basic problem of copying code from Emacs in
accordance with the licence -- e.g. with appropriate copyright notices
-- but I'm sure you'll keep an eye on that.
Cool.
Barry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
iQCUAwUBSYcUgHEjvBPtnXfVAQI16AP3d62FgQ3YTFmpReFPG6X5a1udkj0Uas/d
9DwWOtXT/PZ4+f5MmwuhIO/Ehx3+rlbL3BFwYYHeQgVfgx+LudRZT7zi+A64KhG1
TzhGWCfSPED7DsP0HsDGZDaXuGcWkm/PEWkEi0fvqet5alaOkDi4SA7KTmNijINT
G0yCdQajsg==
=m+IZ
-----END PGP SIGNATURE-----
_______________________________________________
Python-mode mailing list
Python-mode@python.org
http://mail.python.org/mailman/listinfo/python-mode
