From: Christoph Scholtes <cschol2112@googlemail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: python.el cleanup
Date: Tue, 29 Mar 2011 20:58:08 -0600 [thread overview]
Message-ID: <86pqp971rz.fsf@gmail.com> (raw)
In-Reply-To: <jwvhbamcaax.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 29 Mar 2011 09:43:35 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> Could you just clarify why they're considered obsolete (e.g. what would
> the user use instead)?
`python-shell' is not needed since Dave's mode already had
'run-python' to invoke the python interpreter. It offers no advantages
over run-python as far as I can tell except being able to toggle
between a Python and a Jython shell (see below for comments on that).
`python-comint-filter-function' is only called from `python-shell'.
`python-file-queue' is never populated anywhere, only read from
`python-comint filter-function'.
`python-default-interpreter' is only used by `python-shell' and not,
as advertised in its documentation, on first visiting a Python mode
buffer.
`python-python-command-args' and `python-jython-command-args' are only
used in the `python-toggle-shell' function.
`python-which-shell', `python-which-args' and `python-which-bufname'
are used for toggling between the Python and Jython shell.
Finally, `python-toggle-shell'. I think, that we should provide a better
solution for this and therefore remove the current implementation. This
code came from python-mode.el, if I traced that back right.
Python interpreter selection should be universal and not only support Jython
and CPython, but also IronPyton, PyPy etc. I would like to implement a
better solution for this as soon as Fabian's changes are installed. I am
using IronPython quite a bit and it would be nice to be able to switch
flexibly between different interpreters.
Christoph
next prev parent reply other threads:[~2011-03-30 2:58 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 [this message]
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
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=86pqp971rz.fsf@gmail.com \
--to=cschol2112@googlemail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).