From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Barry Warsaw <barry@python.org>
Cc: skip@pobox.com, rms@gnu.org, python-mode@python.org,
XEmacs-Beta@xemacs.org, fx@gnu.org, fbe2@comcast.net,
emacs-devel@gnu.org
Subject: Re: replacing python.el
Date: Sun, 01 Feb 2009 16:57:56 -0500 [thread overview]
Message-ID: <jwvbptl969r.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <6000FD22-0346-46C8-9696-15F54410B64B@python.org> (Barry Warsaw's message of "Sun, 1 Feb 2009 07:33:15 -0500")
> I had hoped that it would be possible to merge python-mode.el and python.el
> and reduce the confusion and inconvenience of Python X/Emacs users.
> Andreas's opinion is that that is technically impossible and I believe it
> is Dave's opinion that it will be practically impossible from a legal
> perspective. If that's the case, then so be it; we will continue to
> develop and maintain python-mode.el as an alternative and XEmacs will
> likely include our version in its distribution. Emacs users will have to
> find it if they are looking for an alternative, but once they do, it should
> work just fine for them.
> python-mode.el is now GPLv3.
I'm glad to hear it's now GPLv3. From Emacs's point of view, we'd like
to see the two converge, but this seems only possible if python-mode.el
can be included in Emacs which requires its code to be assigned to
the FSF. If the copyright assignment is reasonably possible, then
I see no reason why the two code bases can't converge (clearly half the
code would be thrown out, and there may be some tricky political work to
do to get keybindings aligned, etc...).
Last time this was brought up, the general sentiment was that, if
merging is too difficult, it might be preferable to switch wholesale to
python-mode.el (and then maybe try to retrofit some of python.el's
featureset).
> It seems like python-mode.el will never be included in Emacs.
Why is that? Too many contributors? Can't be tracked down?
Won't sign papers?
Stefan
next prev parent reply other threads:[~2009-02-01 21:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4980316B.7080503@online.de>
2009-02-01 6:31 ` replacing python.el Richard M Stallman
2009-02-01 7:00 ` Glenn Morris
2009-02-01 7:58 ` Beverley Eyre
2009-02-01 20:56 ` Dave Love
2009-02-02 2:37 ` Beverley Eyre
2009-02-02 3:37 ` Chong Yidong
2009-02-02 13:39 ` Barry Warsaw
2009-02-02 16:43 ` Richard M Stallman
2009-02-01 12:33 ` Barry Warsaw
2009-02-01 15:42 ` Jeff Kowalczyk
2009-02-02 13:11 ` Barry Warsaw
2009-02-01 21:57 ` Stefan Monnier [this message]
2009-02-02 18:57 ` Barry Warsaw
2009-02-01 20:51 ` Dave Love
2009-02-01 22:03 ` Stefan Monnier
2009-02-02 14:08 ` Barry Warsaw
2009-02-19 20:21 ` ken manheimer
2009-02-19 21:36 ` Barry Warsaw
2009-02-01 22:48 ` Richard M Stallman
2009-02-01 7:55 ` Beverley Eyre
2009-02-01 22:05 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvbptl969r.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=XEmacs-Beta@xemacs.org \
--cc=barry@python.org \
--cc=emacs-devel@gnu.org \
--cc=fbe2@comcast.net \
--cc=fx@gnu.org \
--cc=python-mode@python.org \
--cc=rms@gnu.org \
--cc=skip@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).