-
Notifications
You must be signed in to change notification settings - Fork 10
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
bug: tuple assignment from underpopulated list #15
Comments
It seems like one of the response header did not have a colon. Would you have a copy of the request or response that triggered that? It may be worth patching the code to still add the header (with an empty value) or simply skip. |
Sorry, yes I ended up using curl to work around it.
I concur that it would be worth handling instances like this in a slightly more graceful way to enable parsing of the output. |
Well that case is quite tricky, I don't rely on much to parse the response but the new line character between headers and body is a must have. If I apply what I mentioned, that would creates weird headers (key="This software comes with NO WARRANTY", value="see the file PUBLIC for details.") and likely to block if there is no new line character at all... but I guess that would work in your case (at least not die, and give you access to the response object). Could you add a try/except around the faulty line and send a pull request? Also, interesting response you have there :) |
Yes, well, headers aren't supposed to have spaces, so one way to semi-reliably detect this kind of behavior would be to attempt splitting by Yes, I'll fix a PR. And yes! :-) |
The text was updated successfully, but these errors were encountered: