[issue1778] SyntaxError.offset sometimes wrong

A.M. Kuchling added the comment: Fixed in Python 3.2 alpha 3, so there's no longer any work to be done for this issue. Closing. -- nosy: +akuchling resolution: -> fixed status: open -> closed ___ Python tracker _

[issue1778] SyntaxError.offset sometimes wrong

Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue1778] SyntaxError.offset sometimes wrong

Benjamin Peterson added the comment: None offsets gone in r84931. -- nosy: +benjamin.peterson ___ Python tracker ___ ___ Python-bugs-l

[issue1778] SyntaxError.offset sometimes wrong

Mark Lawrence added the comment: This will go nowhere until someone supplies a patch. I'm assuming unit tests can be built using the attached test file. -- nosy: +BreamoreBoy stage: unit test needed -> needs patch versions: +Python 2.7, Python 3.2 -Python 2.6

[issue1778] SyntaxError.offset sometimes wrong

Daniel Diniz added the comment: Confirmed in trunk and py3k. -- nosy: +ajaksu2 stage: -> test needed versions: +Python 2.6, Python 3.1 -Python 2.4, Python 2.5 ___ Python tracker ___

[issue1778] SyntaxError.offset sometimes wrong

Achim Gaedke added the comment: sometimes offset is None... Example: def blub(bla, blub=None, blabla): bla causes: non-default argument follows default argument Added file: http://bugs.python.org/file9150/compile_test.py __ Tracker <[EMAIL PROTECTED]>

[issue1778] SyntaxError.offset sometimes wrong

Changes by Christian Heimes: -- priority: -> normal __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue1778] SyntaxError.offset sometimes wrong

New submission from Achim Gaedke: The value SyntaxError.offset is for most SyntaxErrors an offset from beginning of line SyntaxError.lineno. In case of an triple-quoted string which is not at all closed, offset seems to be the offset from beginning of the buffer. -- components: Interpret