Sorry it's taken me so long to look into this. I believe I
found the problem but don't know how to fix it, so I'll
describe what I found so that maybe someone with more
lisp-fu than me can solve the problem.
Basically, too much reliance is placed on regular
expressions to determine the end of the first line of a
compound statement. In (py-statement-opens-block-p) it
searches "for a colon with nothing after it except
whitespace, and maybe a comment". Unfortunately, once it
gets there, it's smack dab in the middle of a string. There
is a check for being in a comment, but not one for being in
a string. I somehow think the proper solution might involve
calling (py-in-literal), but I'm having trouble making it
work. If we're in a string we need to keep searching.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=429629
Aiee! Didn't realize there was no formatting in these boxes
( too used to wiki )
breakwithhash.py
Logged In: YES
user_id=44345
Sorry it's taken me so long to look into this. I believe I
found the problem but don't know how to fix it, so I'll
describe what I found so that maybe someone with more
lisp-fu than me can solve the problem.
Basically, too much reliance is placed on regular
expressions to determine the end of the first line of a
compound statement. In (py-statement-opens-block-p) it
searches "for a colon with nothing after it except
whitespace, and maybe a comment". Unfortunately, once it
gets there, it's smack dab in the middle of a string. There
is a check for being in a comment, but not one for being in
a string. I somehow think the proper solution might involve
calling (py-in-literal), but I'm having trouble making it
work. If we're in a string we need to keep searching.