Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

frame numbers in error reporting #76

Open
gabor1 opened this issue Nov 4, 2019 · 2 comments
Open

frame numbers in error reporting #76

gabor1 opened this issue Nov 4, 2019 · 2 comments
Labels
enhancement New feature or request

Comments

@gabor1
Copy link
Contributor

gabor1 commented Nov 4, 2019

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...

@fekad
Copy link
Contributor

fekad commented Nov 4, 2019

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 )

@gabor1
Copy link
Contributor Author

gabor1 commented Nov 4, 2019 via email

@gabor1 gabor1 changed the title line numbers in error reporting frame numbers in error reporting Jan 13, 2021
@gabor1 gabor1 added the enhancement New feature or request label Jan 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants