unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Roehler <andreas.roehler@online.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Tom Roche <Tom_Roche@pobox.com>,
	python-mode@python.org, emacs-devel@gnu.org
Subject: Re: plan for emacs python tooling (esp python.el, python-mode.el)?
Date: Tue, 16 Mar 2010 11:47:57 +0100	[thread overview]
Message-ID: <4B9F61DD.4050507@online.de> (raw)
In-Reply-To: <jwvwrxcq5po.fsf-monnier+emacs@gnu.org>

Stefan Monnier wrote:
>> summary: Is the near-term plan for GNU emacs (e.g. for 2010-2011) to
>> ship with python.el, python-mode.el, both, or something completely
>> different?
> 
> The plan is to ship it with python.el until we can ship it with
> python-mode.el (the barrier being coipyright assignments).
> 
> 
>         Stefan
> 
> 
> 

Hi Stefan,

as far as I understand the OP, the focus is rather the python-environment than the editor.

As far as it concerns editing, python.el, python-mode.el are both suitable IMHO.

Don't see a real gain by switching one for the other. If a precise feature is missed here or there, let's implement it...

Progress would mean having a download source for an environment, which offers all needed at once:
debugging, refactoring, auto-completion etc.

Such an environment should enable emacs editing modes, but vim and other free tools too.


Andreas

--
https://code.launchpad.net/~a-roehler/python-mode
https://code.launchpad.net/s-x-emacs-werkstatt/

  reply	other threads:[~2010-03-16 10:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-15 16:47 plan for emacs python tooling (esp python.el, python-mode.el)? Tom Roche
2010-03-16  3:58 ` Stefan Monnier
2010-03-16 10:47   ` Andreas Roehler [this message]
2010-03-16 11:37     ` Eric M. Ludlam
2010-03-16 14:43       ` Tom Roche

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=4B9F61DD.4050507@online.de \
    --to=andreas.roehler@online.de \
    --cc=Tom_Roche@pobox.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --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).