<?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 using python virtual environments in Model Studio\VDMML in SAS Data Science</title>
    <link>https://communities.sas.com/t5/SAS-Data-Science/using-python-virtual-environments-in-Model-Studio-VDMML/m-p/679401#M8398</link>
    <description>&lt;P&gt;Is there a way to use virutal environments in the Open Source Code node? We have anaconda installed, but will likely need to install some additional packages down the line. I would really prefer using virtual environments in stead of doing installs and updates on a single anaconda installation. I guess we could alternatively run&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;conda list --export &amp;gt; requirements.txt&lt;/PRE&gt;&lt;P&gt;to as a way to save the current working environment before installing or updating something. But I would guess VENV would be a bit easier to roll back if something goes wrong.&lt;/P&gt;&lt;P&gt;Is there some best practice for this in the Model Studio context?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 26 Aug 2020 11:30:55 GMT</pubDate>
    <dc:creator>Ullsokk</dc:creator>
    <dc:date>2020-08-26T11:30:55Z</dc:date>
    <item>
      <title>using python virtual environments in Model Studio\VDMML</title>
      <link>https://communities.sas.com/t5/SAS-Data-Science/using-python-virtual-environments-in-Model-Studio-VDMML/m-p/679401#M8398</link>
      <description>&lt;P&gt;Is there a way to use virutal environments in the Open Source Code node? We have anaconda installed, but will likely need to install some additional packages down the line. I would really prefer using virtual environments in stead of doing installs and updates on a single anaconda installation. I guess we could alternatively run&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;conda list --export &amp;gt; requirements.txt&lt;/PRE&gt;&lt;P&gt;to as a way to save the current working environment before installing or updating something. But I would guess VENV would be a bit easier to roll back if something goes wrong.&lt;/P&gt;&lt;P&gt;Is there some best practice for this in the Model Studio context?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 26 Aug 2020 11:30:55 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Science/using-python-virtual-environments-in-Model-Studio-VDMML/m-p/679401#M8398</guid>
      <dc:creator>Ullsokk</dc:creator>
      <dc:date>2020-08-26T11:30:55Z</dc:date>
    </item>
    <item>
      <title>Re: using python virtual environments in Model Studio\VDMML</title>
      <link>https://communities.sas.com/t5/SAS-Data-Science/using-python-virtual-environments-in-Model-Studio-VDMML/m-p/679763#M8399</link>
      <description>&lt;P&gt;Currently the Open Source Code node in Model Studio does not have a way to invoke a specific virtual environment in the Python install but I do agree that it is useful and will try to look into adding in future release.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When the node executes, the Python executable configured is used to make a call similar to below code where &amp;lt;fileToRun&amp;gt; is constructed on the fly mostly using code from the node editor.&lt;/P&gt;
&lt;PRE&gt;python &amp;lt;fileToRun&amp;gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 27 Aug 2020 15:28:13 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Science/using-python-virtual-environments-in-Model-Studio-VDMML/m-p/679763#M8399</guid>
      <dc:creator>RadhikhaMyneni</dc:creator>
      <dc:date>2020-08-27T15:28:13Z</dc:date>
    </item>
  </channel>
</rss>

