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.

Sign up for GitHub

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

Jump to bottom

Better error reporting #21

Open
GoogleCodeExporter opened this issue Feb 15, 2016 · 1 comment
Open

Better error reporting #21

GoogleCodeExporter opened this issue Feb 15, 2016 · 1 comment
Labels
auto-migrated Component-UI Maintainability Priority-Medium Type-Defect Usability

Comments

@GoogleCodeExporter
Copy link 

Errors don't usually give a whole lot of background, and when the parser
recovers from an error, it often yields strange results.  Should probably
fail more gracefully.

Original issue reported on code.google.com by [email protected] on 25 Mar 2008 at 1:36
@GoogleCodeExporter
Copy link
Author 

Yes, we really ought to use try ... except and the logging module to clean this 
up. The comment "error handling is for wimps" in the source code is not helpful.

Original comment by robb1701 on 27 Sep 2010 at 8:57

  • Added labels: Component-UI, Maintainability, Usability

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Component-UI Maintainability Priority-Medium Type-Defect Usability
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter