<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Python 2 to Python 3 Compatibility in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Python-2-to-Python-3-Compatibility/m-p/493699#M60745</link>
    <description>&lt;P&gt;@dwraesner , this is done per-app - you don't want to mess with Splunk's shipped interpreter. Plus, this really only applies to apps you own; apps that belong to Splunk or other developers should be handled by the owner.&lt;/P&gt;

&lt;P&gt;If you have your own apps that use Python, you can import Python libraries such as Six and Future to make each script compatible with Python 2 and 3. Documentation for using these libraries can be found on the web, for example here: &lt;A href="https://pypi.org/project/six/"&gt;https://pypi.org/project/six/&lt;/A&gt; &lt;/P&gt;</description>
    <pubDate>Tue, 10 Mar 2020 20:29:48 GMT</pubDate>
    <dc:creator>atammana_splunk</dc:creator>
    <dc:date>2020-03-10T20:29:48Z</dc:date>
    <item>
      <title>Python 2 to Python 3 Compatibility</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Python-2-to-Python-3-Compatibility/m-p/493696#M60742</link>
      <description>&lt;P&gt;After running the Splunk Platform Upgrade Readiness App, 1 of many  add-ons / apps on just 1 Splunk Enterprise server that did not pass was the Splunk Add-on for Cisco ISE newest version 3.0.0.  Just this 1 app has 117 python scripts that need to be made compatible, "Required Action: Update these Python scripts to be dual-compatible with Python 2 and 3."&lt;/P&gt;

&lt;P&gt;Does Splunk have a conversion script which can be run, for any app, to convert Python 2 scripts to be dual-compatible? &lt;/P&gt;

&lt;P&gt;If no, then will the Add-on for Cisco ISE be Python 3 compatible?  Also, when will all the other Splunk built add-ons and apps be Python 3 compatible so upgrading to Splunk 8 can proceed?&lt;/P&gt;</description>
      <pubDate>Tue, 10 Mar 2020 15:29:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Python-2-to-Python-3-Compatibility/m-p/493696#M60742</guid>
      <dc:creator>dwraesner</dc:creator>
      <dc:date>2020-03-10T15:29:28Z</dc:date>
    </item>
    <item>
      <title>Re: Python 2 to Python 3 Compatibility</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Python-2-to-Python-3-Compatibility/m-p/493697#M60743</link>
      <description>&lt;P&gt;Hi @dwraesner , the Upgrade Readiness App's most recent version was released on Feb 5, 2020; the newest version for the Add-on for Cisco ISE was released after this, on Feb 11, 2020. The readiness app pulls a static list from Splunkbase before each release. As a result, it likely doesn't know that the newest version of the add-on is actually compatible (and if you look on Splunkbase, you'll see it is). In short, you should be good to go for that app.&lt;/P&gt;

&lt;P&gt;As a note, Splunk does not have a conversion script available, but you can use dual-compatible Python libraries to achieve this.&lt;/P&gt;</description>
      <pubDate>Tue, 10 Mar 2020 17:25:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Python-2-to-Python-3-Compatibility/m-p/493697#M60743</guid>
      <dc:creator>atammana_splunk</dc:creator>
      <dc:date>2020-03-10T17:25:08Z</dc:date>
    </item>
    <item>
      <title>Re: Python 2 to Python 3 Compatibility</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Python-2-to-Python-3-Compatibility/m-p/493698#M60744</link>
      <description>&lt;P&gt;Thanks, currently we're running Splunk Enterprise 7.2.7 which has the $SPLUNK_HOME/Splunk/Python-2.7/Lib folder.  What is the detailed procedure for making these  2.7 lib's also dual compatible with Python 3.x version.&lt;/P&gt;</description>
      <pubDate>Tue, 10 Mar 2020 20:03:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Python-2-to-Python-3-Compatibility/m-p/493698#M60744</guid>
      <dc:creator>dwraesner</dc:creator>
      <dc:date>2020-03-10T20:03:57Z</dc:date>
    </item>
    <item>
      <title>Re: Python 2 to Python 3 Compatibility</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Python-2-to-Python-3-Compatibility/m-p/493699#M60745</link>
      <description>&lt;P&gt;@dwraesner , this is done per-app - you don't want to mess with Splunk's shipped interpreter. Plus, this really only applies to apps you own; apps that belong to Splunk or other developers should be handled by the owner.&lt;/P&gt;

&lt;P&gt;If you have your own apps that use Python, you can import Python libraries such as Six and Future to make each script compatible with Python 2 and 3. Documentation for using these libraries can be found on the web, for example here: &lt;A href="https://pypi.org/project/six/"&gt;https://pypi.org/project/six/&lt;/A&gt; &lt;/P&gt;</description>
      <pubDate>Tue, 10 Mar 2020 20:29:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Python-2-to-Python-3-Compatibility/m-p/493699#M60745</guid>
      <dc:creator>atammana_splunk</dc:creator>
      <dc:date>2020-03-10T20:29:48Z</dc:date>
    </item>
    <item>
      <title>Re: Python 2 to Python 3 Compatibility</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Python-2-to-Python-3-Compatibility/m-p/493700#M60746</link>
      <description>&lt;P&gt;Thanks, downloaded six, and below in quotes is the related documentation I found.  Do you simply copy the six.py file as suggested into the bin directory of the app where the non-compatible .py scripts are located?  I did that, and ran the Upgrade Readiness App on that app again, but the python scripts still do not pass as Python 3 compatible.&lt;/P&gt;

&lt;P&gt;"Six provides simple utilities for wrapping over differences between Python 2 and Python 3. It is intended to support codebases that work on both Python 2 and 3 without modification. six consists of only one Python file, so it is painless to copy into a project."&lt;/P&gt;</description>
      <pubDate>Tue, 10 Mar 2020 21:03:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Python-2-to-Python-3-Compatibility/m-p/493700#M60746</guid>
      <dc:creator>dwraesner</dc:creator>
      <dc:date>2020-03-10T21:03:26Z</dc:date>
    </item>
  </channel>
</rss>

