You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be really nice to report where in the file a problem occurs. e.g. when encountering raise ValueError('All the keys must be unique!'), I want to know which line triggered this in the 4MB input file...
The text was updated successfully, but these errors were encountered:
Do you mean reading the file two times (at the first time just do the checks) or just reporting it on the fly? The error message can tell you that the nth configuration has this problem.
(Unfortunately, I don't have access to the line number because all object are read by ASE )
On 4 Nov 2019, at 18:54, Adam Fekete ***@***.***> wrote:
Do you mean reading the file two times (at the first time just do the checks) or just reporting it on the fly? The error message can tell you that the nth configuration has this problem.
(Unfortunately, I don't have access to the line number because all object are read by ASE )
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
gabor1
changed the title
line numbers in error reporting
frame numbers in error reporting
Jan 13, 2021
It would be really nice to report where in the file a problem occurs. e.g. when encountering
raise ValueError('All the keys must be unique!')
, I want to know which line triggered this in the 4MB input file...The text was updated successfully, but these errors were encountered: