[issue5064] compiler.parse raises SyntaxErrors without line number information

2009-09-04 Thread Georg Brandl
Georg Brandl added the comment: In light of > The compiler package is deprecated in favor of builtin AST. and > It seems a patch would be an enormous undertaking, I guess it's best to close this as "won't fix". -- nosy: +georg.brandl resolution: -> wont fix status: open -> closed

[issue5064] compiler.parse raises SyntaxErrors without line number information

2009-05-21 Thread Jean-Paul Calderone
Jean-Paul Calderone added the comment: It seems a patch would be an enormous undertaking, as the data structure returned by the parser does not include this information, and the parser is written in C. I'll just hack around this somehow. Don't expect a patch from me. -- _

[issue5064] compiler.parse raises SyntaxErrors without line number information

2009-02-06 Thread Neil Schemenauer
Changes by Neil Schemenauer : -- assignee: -> nascheme nosy: +nascheme ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue5064] compiler.parse raises SyntaxErrors without line number information

2009-01-25 Thread Benjamin Peterson
Benjamin Peterson added the comment: Patches are welcome! The compiler package is deprecated in favor of builtin AST. -- nosy: +benjamin.peterson priority: -> low stage: -> needs patch ___ Python tracker

[issue5064] compiler.parse raises SyntaxErrors without line number information

2009-01-25 Thread Jean-Paul Calderone
New submission from Jean-Paul Calderone : Sometimes a syntax error in source passed to `compiler.parse´ causes a `SyntaxError´ with lots of nice information to be raised: >>> from compiler import parse >>> try: ... parse("def f(") ... except SyntaxError, e: ... pass ... >>> e SyntaxError