py-mark-{block,clause} misbehave at beginning of block or clause

[Ed McCardell]

With this Python code:

if foo:
    try:
        pass

calling py-mark-block, py-mark-block-or-clause, or py-mark-clause with point on line 2 will mark the try block, if point is on or before the opening 't' of 'try'.

However, if point is on line 2 but somewhere past the opening 't', like at the end of the line, then the outer if block gets marked, which is unexpected, and different from how it worked in version 6.0.4.

This change is caused by the py-beginning-of-*-p functions, which used to use the py-statement-opens-*-p functions (which returned the same result no matter where you were on the line), but now they don't.

[Andreas Roehler (a-roehler)]

thanks for the report.
BTW bug does not exist in components branch.

[Andreas Roehler (a-roehler)]

please re-open, should you still get it,

thanks,

Andreas