From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Christoph <cschol2112@googlemail.com>
Cc: Chong Yidong <cyd@stupidchicken.com>, Dave Love <fx@gnu.org>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Current state of python.el in the Emacs trunk
Date: Tue, 15 Feb 2011 23:32:09 -0500 [thread overview]
Message-ID: <jwvlj1gk44h.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <86r5b8llwc.fsf@gmail.com> (Christoph's message of "Tue, 15 Feb 2011 20:05:07 -0700")
>> The only problem is that the very reason for desiring such a switch is
>> because nobody (including and especially the most obvious candidate,
>> Dave) has been willing to maintain our python.el.
> I'm confused. Didn't I offer to do maintenance work, like for example
> integrating Dave's bug fixes (if he agreed to it)?
Yes, you did, sorry for that. The discussion of moving to
python-mode.el took place a good while before you suggested taking
over maintenance, so I simplified my argument by not mentioning more
recent developments.
> I have actually spent quite some time digging through the current
> python.el mode and tried to do some clean up and fix things.
> For example, the inital integration of pdbtrack a couple of years ago
> left a huge amount of duplication since it was never really cleaned
> up. For example: why are there two different ways to invoke
> a python shell?
My best guess: historical accident.
>> Now Fabian proposes a third Python mode.
> I looked at it and I like it. It actually fixes some issues that the
> current python.el has, especially when it comes to things like
> pdbtrack. I had some issues getting some of features to work (shell
> completion, for example) but that might just be because I was using
> 24.0.50 and/or using it wrong.
> I didn't have the time to compare the current python.el with Fabian's
> version as far as features go, but I didn't really miss anything while
> using Fabian's new mode today.
Since you have a good knowledge of our current python.el, maybe you
could get together with Fabian to merge the two?
>> Of course, I'd rather work at bringing the various python modes closer
>> to each other, rather than have them fork even further, so I'm not sure
>> what's the best course here.
> As far as python-mode.el goes...the discussion I started on this list
> sparked another on the python-mode list:
> http://mail.python.org/pipermail/python-mode/2011-February/000937.html
> This doesn't sound like we would get on the same page anytime soon.
Don't trust everything you read, and don't assume every poster in
a thread is actually relevant to the problem. AFAIK most authors of
python-mode.el would be willing to sign the needed papers and work with
us, but it's indeed likely that one or two might pose problem, and even
more likely that it'll take a lot of effort (if at all possible) to
track down all those people.
And furthermore, we don't need to integrate python-mode.el into Emacs to
bring the various python mode closer to each other.
Stefan
next prev parent reply other threads:[~2011-02-16 4:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 4:32 Current state of python.el in the Emacs trunk Christoph
2011-01-27 18:35 ` Stefan Monnier
2011-01-28 0:23 ` Christoph
2011-02-15 20:07 ` Dave Love
2011-02-15 20:13 ` Chong Yidong
2011-02-15 22:33 ` Stefan Monnier
2011-02-16 3:05 ` Christoph
2011-02-16 4:32 ` Stefan Monnier [this message]
2011-02-21 0:49 ` Dave Love
2011-02-16 7:07 ` Fabian Ezequiel Gallina
2011-02-21 0:52 ` Dave Love
2011-02-21 0:51 ` Dave Love
2011-02-24 6:13 ` Christoph
2011-03-29 4:58 ` ken manheimer
2011-03-29 14:03 ` Stefan Monnier
2011-03-29 15:34 ` Fabian Ezequiel Gallina
2011-03-30 2:12 ` Christoph Scholtes
2011-02-21 0:48 ` Dave Love
2011-02-21 2:10 ` Stephen J. Turnbull
2011-02-21 2:25 ` Stephen J. Turnbull
2011-02-21 22:25 ` Stefan Monnier
2011-02-21 0:48 ` Dave Love
-- strict thread matches above, loose matches on Subject: below --
2011-01-27 9:33 Андрей Парамонов
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=jwvlj1gk44h.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=cschol2112@googlemail.com \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=fx@gnu.org \
/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).