unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Andreas Röhler" <andreas.roehler@online.de>
To: emacs-devel@gnu.org
Cc: Christoph <cschol2112@googlemail.com>,
	Barry Warsaw <barry@python.org>,
	python-mode@python.org
Subject: Re: [Python-mode] python.el cleanup
Date: Sun, 03 Apr 2011 20:55:12 +0200	[thread overview]
Message-ID: <4D98C290.60205@online.de> (raw)
In-Reply-To: <4D98B236.40906@gmail.com>

Am 03.04.2011 19:45, schrieb Christoph Scholtes:
> Hi Andreas,
>
> On 3/30/2011 8:10 AM, Andreas Röhler wrote:
>
>> glad to see Emacs python facilities improve. As you mention
>> python-mode.el, there are some remarks in python.el which I feel are not
>> correct. If some solution predates historically another, there are
>> usually some setbacks from being the first.
>
> I am not sure which remarks you are referring to here.

Hi Christoph,

reading for example:

;; That isn't covered by an FSF copyright assignment (?), unlike this
;; code, and seems not to be well-maintained for Emacs (though I've
;; submitted fixes).


>
>> OTOH from my perspective python-mode.el has still some point in
>> proceding.
>
> I don't think anybody is saying otherwise.
>
>> Hopefully we may discuss the pro and cons to the benefit of users, which
>> flavour they may choose finally. As you might have been remarked, its
>> interwoven to an extend, you can seldom discern it clearly to the one or
>> other origin.
>
> To me, it really doesn't matter where it originated from or who was
> first. If it works great, great, if it does not, let's improve it. The
> goal should be the best Python support for Emacs possible.
>
>> BTW I'm not blaming the GNU's side. Just wanted to point at the issue so
>> we might hopefully reduce the obstacles.
>
> Here, I am also not sure what issue or obstacles you are referring to.
>

Assume people will rather not be inclined to send bug reports, resp. 
fixes, if feeling quitted with remarks telling their own baby not being 
well maintained. That I would call an obstacle.


Andreas

> Christoph
>
>




  reply	other threads:[~2011-04-03 18:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-29  2:34 python.el cleanup Christoph Scholtes
2011-03-29 13:43 ` Stefan Monnier
2011-03-30  2:58   ` Christoph Scholtes
2011-03-30 14:10     ` Andreas Röhler
2011-03-30 18:48       ` Barry Warsaw
2011-04-03 17:45       ` [Python-mode] " Christoph Scholtes
2011-04-03 18:55         ` Andreas Röhler [this message]
2011-04-04 14:35           ` Stefan Monnier
2011-04-04 15:21           ` Barry Warsaw
2011-04-04 21:46             ` [Python-mode] " Stefan Monnier
2011-04-04 21:51               ` Barry Warsaw
2011-04-05  0:07                 ` skip
2011-04-04 22:24               ` [Python-mode] " Glenn Morris
2011-04-05  6:27                 ` Andreas Röhler
2011-04-05 13:52                   ` Stefan Monnier
2011-03-30 14:35     ` 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=4D98C290.60205@online.de \
    --to=andreas.roehler@online.de \
    --cc=barry@python.org \
    --cc=cschol2112@googlemail.com \
    --cc=emacs-devel@gnu.org \
    --cc=python-mode@python.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).