➜

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.

classification
Title: python-mode py-execute-buffer bug
Type: Stage:
Components: Demos and Tools Versions: Python 2.4
process
Status: closed Resolution:
Dependencies: Superseder:
Assigned To: skip.montanaro Nosy List: jjlee, skip.montanaro
Priority: normal Keywords: patch

Created on 2003-07-29 20:29 by jjlee, last changed 2022-04-10 16:10 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
bh2 jjlee, 2003-07-29 20:29
Messages (2)
msg44365 - (view) Author: John J Lee (jjlee) Date: 2003-07-29 20:29 
The rest of this report is a quote from Skip's message in 
c.l.py. 
 
Attached is Skip's tentative patch (which is likely 
incorrect for Jython). 
 
--------------------------------- 
    John> 1. Why do I get this in my minibuffer when I do 
    John> C-c C-c in a python-mode buffer containing the 
    John> following valid Python code? 
 
    John> Wrong type argument: sequencep, cpython 
 
It looks like a bug in py-execute-region.  It sets the shell 
variable like so: 
 
        (setq shell (or (py-choose-shell-by-shebang) 
(py-choose-shell-by-import) py-which-shell)))) 
 
which gives it the value (quote cpython).  Later on it tries 
to concatenate it: 
 
      (let ((cmd (concat shell (if (string-equal 
py-which-bufname "JPython") " -" "")))) 
 
which fails because shell is not a string (strictly 
speaking, a sequence) at that point.  I'm not sure what 
the correct fix is.
msg44366 - (view) Author: Skip Montanaro (skip.montanaro) * (Python triager) Date: 2003-08-05 03:35 
Logged In: YES 
user_id=44345

migrated to python-mode project.  follow it here:

https://sourceforge.net/tracker/
index.php?func=detail&aid=783262&group_id=86916&ati
d=581351
History
Date User Action Args
2022-04-10 16:10:20adminsetgithub: 38965
2003-07-29 20:29:27jjleecreate