Remove ResultsReader, six
#670
Open
Conversation
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
This was
linked to
issues
Sep 9, 2025
szykol
reviewed
Sep 10, 2025
szykol
approved these changes
Sep 10, 2025
Ickerday
force-pushed
the
dev/BJ/SDK-76-remove-deprecation
branch
from
a80249a to
06d332d
Compare
|
Once this will be released in v2.1.2, |
|
@TwilightMercy correct, although we still depend on python-dotenv. |
Built in in Splunk modules? |
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.
I think it's high time to get rid of the old
ResultsReader. We deprecated it in 1.6.19 (#441), we're at 2.2.0a0 now.Additionally, I removed
sixas it's been years since we migrated to Python 3 fully and the library isn't used anywhere anymore