| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
string with text in column zero. Skip that stuff when looking for the
"first statement following the statement containing point".
|
|
|
|
|
| |
save-excursion so that when the function is complete, point is
preserved.
|
|
|
|
| |
define info-lookup-maybe-add-help.
|
|
|
|
|
| |
the `when' condition so other non-Python shell comint changes won't
cause random buffers to pop.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
better auto-recognition of a Jython file vs. a CPython (or agnostic)
file by looking at the #! line more closely, and inspecting the import
statements in the first 20000 bytes (configurable). Specifically,
(py-import-check-point-max): New variable, controlling how far into
the buffer it will search for import statements.
(py-jpython-packages): List of package names that are Jython-ish.
(py-shell-alist): List of #! line programs and the modes associated
with them.
(jpython-mode-hook): Extra hook that runs when entering jpython-mode
(what about Jython mode? <20k wink>).
(py-choose-shell-by-shebang, py-choose-shell-by-import,
py-choose-shell): New functions.
(python-mode): Use py-choose-shell.
(jpython-mode): New command.
(py-execute-region): Don't use my previous hacky attempt at doing
this, use the new py-choose-shell function.
One other thing this file now does: it attempts to add the proper
hooks to interpreter-mode-alist and auto-mode-alist if they aren't
already there. Might help with Emacs users since that editor doesn't
come with python-mode by default.
|
|
|
|
|
| |
whitespace can hose the needs-if test. So just skip all blank lines
at the start of the region right off the bat.
|
|
|
|
|
| |
always get to see the result of e.g. a py-execute-region. Funny, this
bugged both me /and/ Guido!
|
|
|
|
|
|
|
|
|
| |
Allows for some customization of the underlying comint buffer.
(py-shell): Call the new hook.
(info-lookup-maybe-add-help): A new call suggested by Milan Zamazal to
make lookups in the Info documentation easier.
|
|
|
|
|
|
|
|
| |
(py-mode-map): Bind py-help-at-point to f1 as well as C-c C-h
(py-help-at-point): Make sure the symbol is quoted so things like
pydoc.help('sys.platform') work correctly. Also, leave the *Python
Output* buffer in help-mode; this may be a bit more controversial.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to call pychecker on the current file, add a face for pseudo
keywords self, None, True, False, and Ellipsis. Specifically,
(py-pychecker-command, py-pychecker-command-args): New variables.
(py-pseudo-keyword-face): New face variable, defaulting to a copy of
font-lock-keyword-face.
(python-font-lock-keywords): Add an entry for self, None, True, False,
Ellipsis to be rendered in py-pseudo-keyword-face.
(py-pychecker-history): New variable.
(py-mode-map): Bind C-c C-w to py-pychecker-run.
(py-pychecker-run): New command.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
"help-on-symbol-at-point" feature which uses pydoc to provide help on
the symbol under point, if available.
Mods include some name changes, a port to Emacs, binding the command
to C-c C-h, and providing a more informative error message if the
symbol's help can't be found (through use of a nasty bare except).
Note also that py-describe-mode has been moved off of C-c C-h m; it's
now just available on C-c ?
Closes SF patch #545439.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
#! line, use the command on that line as the shell command to use to
execute the region. I.e. if the region looks like
----------------
#! /usr/bin/env python1.5
print 'hello world'.startswith('hello')
----------------
you'll get an exception! :)
This closes SF bug #232398.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
python-mode file, py-which-shell would have been nil and the command
to use would not get set correctly. This changes things so that 1)
the temporary file has a .py extension, 2) the temporary file is put
into python-mode, and 3) the temporary file's py-which-shell is
captured in a local `shell' variable, which is used to calculate the
command to use. Closes SF bug #545436.
(py-parse-state): Rip out the XEmacs-specific calls to
buffer-syntactic-context, which can get quite confused if there's an
open paren in column zero say, embedded in a triple quoted string.
This was always a performance hack anyway, and computers are fast
enough now that we should be able to get away with the slower, more
portable, full-parse branch. Closes SF bug #451841.
Update the comments at the top of the file.
|
|
|
|
|
|
| |
searches. This is added after /tmp. Closes SF bug #505488, except
that /var/tmp comes after /tmp instead of the patch's suggestion of
putting it before /usr/tmp.
|
|
|
|
|
|
|
|
|
| |
implementation to match the documentation for
py-honor-comment-indentation w.r.t. not nil or t value. In that case
it should still ignore ## for indentation purposes. Closes SF bug
#523825, w/ patch provided by Christian Stork (mod'd by Barry).
Python 2.2.1 candidate.
|
|
|
|
| |
clobbered on checkin.
|
|
|
|
|
|
|
|
| |
additional offset is only applied to continuation lines for block
opening statements.
(py-compute-indentation): Only add py-continuation-offset if
py-statement-opens-block-p is true.
|
|
|
|
| |
new "simple generators" feature of 2.2. See PEP 255.
|
|
|
|
|
|
|
| |
indent continuation lines, defined as lines following those that end
in backslash.
(py-compute-indentation): Support for py-continuation-offset.
|
|
|
|
| |
prefix to the message lines.
|
| |
|
|
|
|
| |
multi-line list comprehensions.
|
|
|
|
| |
buffer after executing its contents.
|
|
|
|
|
| |
but only in "import foo as bar" statements (including optional
preceding `from' clause).
|
|
|
|
|
|
| |
delimiter, watch out for backslash escaped delimiters. Also use =
instead of eq for character comparison (because a character is = to
it's integer value, but not eq to it).
|
|
|
|
| |
the insertion of the text.
|
|
|
|
|
|
| |
Montanaro, handle execution of indented regions by inserting an "if
1:" in front of the block. This better preserves things like triple
quoted strings and commented regions. This patch resolves PR#264.
|
|
|
|
|
| |
convenient to call py-shell before the first Python file has been
visited.
|
|
|
|
|
|
|
| |
(python): Set defgroup :prefix to "py-" to make variable names cleaner.
(py-jpython-command, py-jpython-command-args): Set :tag for proper
capitalization of JPython in variable name display.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
first time a py buffer is visited during the Emacs session. This
ensures that py-which-shells is initialized and also guarantees that
the mode lines reflect the correct shell. First bug found by GvR,
second one has long bugged :) me.
(py-toggle-shells): Programmatically, arg can also take the symbols
`cpython' or `jpython', which makes it easy to call with the value of
py-default-interpreter.
(py-shell): Don't need to initialize py-which-* variables since these
will guarantee to be initialized by python-mode when the first py
buffer is visited.
(py-default-interpreter): Update docstring.
|
|
|
|
| |
regex match actually succeeded!
|
|
|
|
| |
the line's whitespace. back-to-indentation should /follow/ this call.
|
|
|
|
|
|
| |
casing when py-honor-comment-indentation is nil, but this could be a
religious issue with some. Seems to me we should still be dedenting
such comment lines one level.
|
|
|
|
|
|
| |
buffer-syntactic-context -- just short circuit the TQS test by jumping
to point-min and doing the test from there. For long files, this will
be faster than looping with a re-search-backwards.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
indentation when the return value is a multiline sexp:
def bug():
try:
if 2>1:
return (11+
12)
else: #XXX
return 12
except:
return 13
|
|
|
|
| |
switches to pass into the shell process (only on initial startup).
|
|
|
|
|
| |
or JPython is the default interpreter to use when `C-c !' is entered
for the first time.
|
|
|
|
| |
py-newline-and-indent.
|
|
|
|
|
|
|
|
|
|
|
| |
py-newline-and-indent. These ought to get picked up by the mapcar
that follows; any existing binding to newline-and-indent gets shadowed
to py-newline-and-indent.
This will break some people who, e.g. bind C-m or C-j to newline but
still want these bound to py-newline-and-indent in Python mode. On
the other hand, the forced binding pisses off Emacs diehards. So
consider this experimental and see if any tall Dutch guys complain :-)
|
|
|
|
|
|
| |
standard narrow-to-defun but works with Python classes and methods.
With no arg, narrows to most enclosing def/method. With C-u arg,
narrows to most enclosing class.
|
|
|
|
| |
for delete forwardness.
|
|
|
|
| |
(e.g. except: on first line of buffer).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
string we find ourselves in, based on the passed in delimiter.
(py-compute-indentation): Fixes for indentation errors when we land
inside a triple quoted string. For example:
def foo():
if os.path.isfile(o_pri_mbox_file) and os.path.isfile(o_pub_mbox_file):
print """\
I found both a private and a public mbox archive file
private: %s
public : %s
I won't move either file, but you should choose one and move it to
%s
You may want to merge them manually, but be careful about exposing private
correspondences to the public.""" % (
o_pri_mbox_file, o_pub_mbox_file, mbox_file)
*----indentation would be wrong on this line.
|
|
|
|
|
| |
semantics between CPython/JPython when the script source is piped to
stdin.
|
|
|
|
| |
correct Python shell (CPython or JPython).
|
|
|
|
| |
generalize the matching of function arguments.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
#simple things. First step: rename the Imenu supportive variables and
#functions in this file to py-imenu-* so I can grok what is part of
#python-mode and what is part of Imenu.
(py-imenu-create-index-engine): Fixed problem with two classes in a
single file, caused by new semantics of py-beginning-of-def-or-class
when called programmatically.
#Note, there are still some problems with Imenu when arguments to
#functions are funky, but it should be much better now.
|
|
|
|
| |
#checkin script.
|
| |
|