unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Richard Riley <rileyrgdev@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Best way to run python code within Emacs?
Date: Thu, 11 Dec 2008 11:49:38 +0100	[thread overview]
Message-ID: <ghqrb2$31f$1@rileyrgdev.motzarella.org> (raw)
In-Reply-To: 3a313093-3f59-4d88-940a-8555d7a364c9@i18g2000prf.googlegroups.com

"seberino@spawar.navy.mil" <seberino@spawar.navy.mil> writes:

> I know how to start a shell in Emacs and from there start the Python
> interpreter in Emacs.
>
> Is there a better/faster way to run Python code I'm working on?
>
> Chris

http://www.emacswiki.org/emacs/PythonMode#toc10

Not Emacs 23 specific I expect. But all the info you need is there I
think. Means knowing about paths and locating necessary packages though.


      parent reply	other threads:[~2008-12-11 10:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-10 22:07 Best way to run python code within Emacs? seberino
2008-12-10 23:07 ` Ian Eure
2008-12-11  6:09   ` Kevin Rodgers
2008-12-11 10:49 ` Richard Riley [this message]

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='ghqrb2$31f$1@rileyrgdev.motzarella.org' \
    --to=rileyrgdev@gmail.com \
    --cc=help-gnu-emacs@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.
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).