Skip to content

Conversation

Ickerday
Copy link
Collaborator

@Ickerday Ickerday commented Sep 9, 2025

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 the local copy of six and instead added it as an optional dependency group under compat. This might get reverted - ideally we shouldn't be needing this file, but I asked around and there might be issues with removing six entirely because of all apps sharing one interpreter.

@Ickerday Ickerday force-pushed the dev/BJ/SDK-76-remove-deprecation branch from a80249a to 06d332d Compare September 15, 2025 14:46
@TwilightMercy
Copy link

Once this will be released in v2.1.2,
There will be no longer dependency requirements of packaging + deprecation modules?

@Ickerday
Copy link
Collaborator Author

@TwilightMercy correct, although we still depend on python-dotenv.

@TwilightMercy
Copy link

TwilightMercy commented Sep 19, 2025

@TwilightMercy correct, although we still depend on python-dotenv.

Built in in Splunk modules?

@Ickerday Ickerday merged commit 306d3f8 into develop Sep 22, 2025
6 checks passed
@Ickerday Ickerday deleted the dev/BJ/SDK-76-remove-deprecation branch September 22, 2025 15:11
@Ickerday
Copy link
Collaborator Author

Ickerday commented Sep 22, 2025

Built in in Splunk modules?

Any dependencies should be packaged with your Splunk app as described here. Please let us know if you can't find the info you need in the docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

No deprecation library in splunk SDK Splunk SDK has dependencies not satisfied by Splunk Python
3 participants