Better string handling for dogwrap and python3 support#379
Merged
Conversation
gzussa
approved these changes
May 28, 2019
Contributor
gzussa
left a comment
There was a problem hiding this comment.
Much better!! and clean description. Thanks for this fix! Should we add tests to make sure it solves the issue?
|
Sorry for the delay in testing, but got to it today. It works! In our testing, dogwrap stays alive and no more database breakdown on unicode output! +1 on adding tests ;-) We'd love for this to get merged to master and available via pip install :) |
Contributor
Author
|
Thanks for testing this @synth, we'll likely do a release on PyPI this week |
This was referenced Jun 4, 2019
dabcoder
pushed a commit
to dabcoder/datadogpy
that referenced
this pull request
Oct 25, 2019
dabcoder
pushed a commit
to dabcoder/datadogpy
that referenced
this pull request
Nov 28, 2019
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
writeexpects bytes.Resolves #371, closes #223