Conversation
armenzg
approved these changes
Mar 17, 2021
evanpurkhiser
approved these changes
Mar 17, 2021
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
Trove classifer for 3.8 doesn't exist, but 3.7 was added in 0.27.0.
We don't use threadstats in production, but I'm thinking of switching over to it in the future. In that case, 0.29.3 is a good version (DataDog/datadogpy#370, DataDog/datadogpy#390).
This is a pretty big jump, but most of the changes are not related to Dogstatsd or threadstats (except, 0.19.0 has a notable fix for threadstats, but again we don't use it in production right now) - they're mostly datadog API client related.
I also looked at
uwsgi-dogstatsd, we're fine there.