Issue 232398: Emacs Python mode bugs (original) (raw)

Issue232398

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

This issue has been migrated to GitHub: https://github.com/python/cpython/issues/33925

classification

process

Created on 2001-02-14 21:12 by gvanrossum, last changed 2022-04-10 16:03 by admin. This issue is now closed.

Messages (5)
msg3348 - (view)	Author: Guido van Rossum (gvanrossum) *	Date: 2001-02-14 21:12
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.
msg3349 - (view)	Author: Barry A. Warsaw (barry) *	Date: 2001-02-23 18:37
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.
msg3350 - (view)	Author: Jeremy Hylton (jhylton)	Date: 2002-03-01 22:51
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?
msg3351 - (view)	Author: Barry A. Warsaw (barry) *	Date: 2002-03-01 23:03
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.
msg3352 - (view)	Author: Barry A. Warsaw (barry) *	Date: 2002-04-22 16:23
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.