[Python-bugs-list] [ python-Bugs-232398 ] Emacs Python mode bugs

noreply@sourceforge.net noreply@sourceforge.net
Mon, 22 Apr 2002 09:23:55 -0700


Bugs item #232398, was opened at 2001-02-14 16:12
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=232398&group_id=5470

Category: Demos and Tools
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Guido van Rossum (gvanrossum)
Assigned to: Barry Warsaw (bwarsaw)
Summary: Emacs Python mode bugs

Initial Comment:
1. I wish that Emacs Python mode, when I run a buffer with ^C^C,
looked at the #! line (if there is one) to choose a Python interpreter,
rather than blindly using the default.

2. Also, when I set the variable python-command to "python1.5", this apparently has no effect -- it still uses "python".

3. Maybe I've submitted this before; each time I use ^C^CF a new buffer with a name like /usr/tmp/python-uKA1TJ is created; these buffers just collect dust.

----------------------------------------------------------------------

>Comment By: Barry Warsaw (bwarsaw)
Date: 2002-04-22 12:23

Message:
Logged In: YES 
user_id=12800

Note that I can't reproduce #2 anymore.

python-mode.el 4.10 implements the suggested feature in item #1.


----------------------------------------------------------------------

Comment By: Barry Warsaw (bwarsaw)
Date: 2002-03-01 18:03

Message:
Logged In: YES 
user_id=12800

I'll handle it.  I've got a bunch of minor python-mode
requests backed up, just waiting for a lull to be attacked.
 Please keep this open.

----------------------------------------------------------------------

Comment By: Jeremy Hylton (jhylton)
Date: 2002-03-01 17:51

Message:
Logged In: YES 
user_id=31392

Barry,

Are you still planning to work on this?  Or should we move 
it to feature requests and close the bug report?


----------------------------------------------------------------------

Comment By: Barry Warsaw (bwarsaw)
Date: 2001-02-23 13:37

Message:
I've fixed #3 in 3.110 of python-mode.el.  The other two will require some non-trivial recoding py-execute-region and the py-which-* variables.  I'm not immediately sure of the best way to do this, but I'll work on this for 2.1 final.

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=232398&group_id=5470