Skip to content

CLN: let URLError fall through in pandas.io.html._read #4305

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 1 commit into from
Jul 25, 2013
Merged

CLN: let URLError fall through in pandas.io.html._read #4305

merged 1 commit into from
Jul 25, 2013

Conversation

cpcloud
Copy link
Member

@cpcloud cpcloud commented Jul 20, 2013

No description provided.

@ghost ghost assigned cpcloud Jul 20, 2013
@cpcloud
Copy link
Member Author

cpcloud commented Jul 20, 2013

cc @jtratner
#4303

@jtratner
Copy link
Contributor

@cpcloud handling network IO is clearly tricky. Were you able to recreate the conditions for the error that was initially raised with the original URL?

@cpcloud
Copy link
Member Author

cpcloud commented Jul 20, 2013

nope. just skipping for now if raising IOError (this is what the network decorator does), but there's something going on with a bogus url that i'm passing in tests with unicode not sure what yet

@cpcloud
Copy link
Member Author

cpcloud commented Jul 20, 2013

marking for 0.13 because i'm not sure if i'll be able to get this by this weekend

A skip will now occur if a call to urlopen or a read from the resulting object
throws a urllib2.URLError exception
cpcloud added a commit that referenced this pull request Jul 25, 2013
CLN: let URLError fall through in pandas.io.html._read
@cpcloud cpcloud merged commit c722914 into pandas-dev:master Jul 25, 2013
@cpcloud cpcloud deleted the add-urlerror-info branch July 25, 2013 00:00
@cpcloud
Copy link
Member Author

cpcloud commented Jul 25, 2013

oh phooey i put in 0.12 release notes 😑

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants