Ticket #71 (new enhancement)
Secret translation of .sage to .py causes confusion
|Reported by:||Justin Walker (justin@…||Owned by:||cwitty|
When a .sage file is "load"ed or "attach"ed, it gets translated to a .py file before being processed; the result is a file with different structure than the original. Any errors are described in terms of the .py file, not the .sage file. I realize this is a kind of Catch-22, but is there a way to (as the C preprocessor does) keep the .sage line numbers?
Of course this requires that Python have that ability, because it reports the errors.
I suppose the proper solution, given this, is to document the issue.
I think this points up an aspect of a fundamental issue: SAGE is a programming language/system; SAGE is a computer system for mathematicians to use. I'm not sure how good it can be at both.
- Owner changed from somebody to cwitty
- Component changed from basic arithmetic to misc
- Summary changed from Secret transation of .sage to .py causes confusion to Secret translation of .sage to .py causes confusion