YAML parser occasionally gets non-string responses. Protect against them. #7

Merged
merged 1 commit into from Sep 25, 2011

Projects

None yet

2 participants

@aahoughton
Contributor

No description provided.

@pascalopitz pascalopitz merged commit 98fae08 into pascalopitz:master Sep 25, 2011
@pascalopitz
Owner

Thank you!

@aahoughton
Contributor

You're welcome! Any chance you can bump the minor version number so I can use the canonical repo again? After you're comfortable with it -- it's not clear that simply returning str, when it's not a 'string', is the right thing to do in every case -- but it's made a huge difference for us.

@pascalopitz
Owner

No problem ... done.
I haven't really had the time to support this library as much as it probably deserves, and I am not using it at the moment at all.
But I am open to suggestions.

What are the non string responses exactly? How should they be handled?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment