Force Python 3.9 since that's what we need for our scripts to run #80
Conversation
This file contains 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
aviau
approved these changes
Jan 16, 2025
Updated the Splunk upload to 9.4
TyMarc
force-pushed
the
mahinse/dont_force_python_versin
branch
from
707ee3e to
fd2209a
Compare
|
Even the new Splunk AppInspect is returning a validation error if you force the python version to python 3.9, even if it's part of the available options: https://docs.splunk.com/Documentation/Splunk/latest/Admin/Restmapconf
|
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.
If a customer needs to force a custom python version for their application to run, this will make sure our scripts will still run using Python 3.9