Skip to content

Deal with etree not being able to parse the document better #50

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

Merged
merged 2 commits into from
Jul 3, 2013

Conversation

jlward
Copy link
Contributor

@jlward jlward commented Jul 3, 2013

Right now a nasty SyntaxError is raised. Instead make a custom exception and raise that guy instead.

@ghost ghost assigned jlward Jul 3, 2013
@winhamwr
Copy link
Contributor

winhamwr commented Jul 3, 2013

Good idea. Looks good. At some point, you'll probably want to implement an exceptions hierarchy, with all pydocx exceptions inheriting from a base pydocx exception.

@jlward
Copy link
Contributor Author

jlward commented Jul 3, 2013

I already thought of that, I decided to punt for now since there is only one exception.

jlward added a commit that referenced this pull request Jul 3, 2013
Deal with etree not being able to parse the document better
@jlward jlward merged commit a47c8bc into master Jul 3, 2013
jlward pushed a commit that referenced this pull request Mar 14, 2014
jlward added a commit that referenced this pull request Mar 14, 2014
Deal with etree not being able to parse the document better
jlward pushed a commit that referenced this pull request Mar 14, 2014
jlward added a commit that referenced this pull request Mar 14, 2014
Deal with etree not being able to parse the document better
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants