https://community.splunk.com/t5/Splunk-Dev/Is-it-necessary-to-put-shebang-on-custom-scripts/m-p/607420#M10722 <P>The correct form of shebang for python3 is</P><PRE>#!/usr/bin/env python3</PRE><P>But that's not the main point here.</P><P>Splunk should spawn its own python instance for python script regardless of the shebang (and shebang allows for easy testing outside of splunk environment)</P> Thu, 28 Jul 2022 20:18:57 GMT PickleRick 2022-07-28T20:18:57Z https://community.splunk.com/t5/Splunk-Dev/Is-it-necessary-to-put-shebang-on-custom-scripts/m-p/607417#M10721 <P>Is it necessary to put `shebang` on custom Python script that will be executed by `splunk`? The reason why I ask is because `shebang` is `#!/usr/local/bin/python` but we know that Spunk uses the one $SPLUNK_HOME/bin/python3.</P><P>&nbsp;</P><P>Thanks in advance.</P> Thu, 28 Jul 2022 19:25:05 GMT https://community.splunk.com/t5/Splunk-Dev/Is-it-necessary-to-put-shebang-on-custom-scripts/m-p/607417#M10721 morethanyell 2022-07-28T19:25:05Z https://community.splunk.com/t5/Splunk-Dev/Is-it-necessary-to-put-shebang-on-custom-scripts/m-p/607420#M10722 <P>The correct form of shebang for python3 is</P><PRE>#!/usr/bin/env python3</PRE><P>But that's not the main point here.</P><P>Splunk should spawn its own python instance for python script regardless of the shebang (and shebang allows for easy testing outside of splunk environment)</P> Thu, 28 Jul 2022 20:18:57 GMT https://community.splunk.com/t5/Splunk-Dev/Is-it-necessary-to-put-shebang-on-custom-scripts/m-p/607420#M10722 PickleRick 2022-07-28T20:18:57Z