<?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>idea Enhance the Python Package Manager to handle pip packages in ArcGIS Pro Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-ideas/enhance-the-python-package-manager-to-handle-pip/idi-p/934556</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;While you can use pip to install a package in a conda Python environment, such packages &lt;EM&gt;&lt;STRONG&gt;do not appear&lt;/STRONG&gt;&lt;/EM&gt; in the ArcGIS Pro Python Package Manager, leaving an un-savvy user with a &lt;EM&gt;misleading understanding&lt;/EM&gt; of which Python modules are actually installed in a given environment. However, the 'conda list' command will display &lt;EM&gt;&lt;STRONG&gt;all&lt;/STRONG&gt; &lt;/EM&gt;installed modules in a conda environment, including those installed using pip. It would be &lt;EM&gt;&lt;STRONG&gt;very nice&lt;/STRONG&gt;&lt;/EM&gt; if the Python Package Manager would at least &lt;EM&gt;display&lt;/EM&gt; packages installed with pip, like the 'conda list' command. (With the understanding that package metadata other than version would be unavailable for the pip-installed packages, since pip packages do no include conda metadata.) For extra credit, it would be &lt;EM&gt;&lt;STRONG&gt;really great&lt;/STRONG&gt;&lt;/EM&gt; if the Python Module Manager were able to search for and&amp;nbsp;&lt;EM&gt;install&lt;/EM&gt; pip packages.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Justification: Many Python modules are available for installation via pip rather than conda. In many cases&amp;nbsp;where both conda and pip packages are available for a given Python module, the conda package will be several versions behind the pip version. If you need the latest and greatest for a given Python module, often &lt;STRONG&gt;&lt;EM&gt;only&lt;/EM&gt;&lt;/STRONG&gt; a pip package will be available. The reason for this is that pip is the primary&amp;nbsp;installation tool for pure Python modules in the larger Python community. (Conda, on the other hand, offers built-in environment management, and can handle distribution of non-Python dependencies, which pip cannot. So while it's not as ubiquitous as pip, conda is a technically superior tool for managing Python installations, and a good choice for Python module/environment management in ArcGIS Pro.)&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 11 Jun 2019 21:59:41 GMT</pubDate>
    <dc:creator>TracyThorleifson</dc:creator>
    <dc:date>2019-06-11T21:59:41Z</dc:date>
    <item>
      <title>Enhance the Python Package Manager to handle pip packages</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/enhance-the-python-package-manager-to-handle-pip/idi-p/934556</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;While you can use pip to install a package in a conda Python environment, such packages &lt;EM&gt;&lt;STRONG&gt;do not appear&lt;/STRONG&gt;&lt;/EM&gt; in the ArcGIS Pro Python Package Manager, leaving an un-savvy user with a &lt;EM&gt;misleading understanding&lt;/EM&gt; of which Python modules are actually installed in a given environment. However, the 'conda list' command will display &lt;EM&gt;&lt;STRONG&gt;all&lt;/STRONG&gt; &lt;/EM&gt;installed modules in a conda environment, including those installed using pip. It would be &lt;EM&gt;&lt;STRONG&gt;very nice&lt;/STRONG&gt;&lt;/EM&gt; if the Python Package Manager would at least &lt;EM&gt;display&lt;/EM&gt; packages installed with pip, like the 'conda list' command. (With the understanding that package metadata other than version would be unavailable for the pip-installed packages, since pip packages do no include conda metadata.) For extra credit, it would be &lt;EM&gt;&lt;STRONG&gt;really great&lt;/STRONG&gt;&lt;/EM&gt; if the Python Module Manager were able to search for and&amp;nbsp;&lt;EM&gt;install&lt;/EM&gt; pip packages.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Justification: Many Python modules are available for installation via pip rather than conda. In many cases&amp;nbsp;where both conda and pip packages are available for a given Python module, the conda package will be several versions behind the pip version. If you need the latest and greatest for a given Python module, often &lt;STRONG&gt;&lt;EM&gt;only&lt;/EM&gt;&lt;/STRONG&gt; a pip package will be available. The reason for this is that pip is the primary&amp;nbsp;installation tool for pure Python modules in the larger Python community. (Conda, on the other hand, offers built-in environment management, and can handle distribution of non-Python dependencies, which pip cannot. So while it's not as ubiquitous as pip, conda is a technically superior tool for managing Python installations, and a good choice for Python module/environment management in ArcGIS Pro.)&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Jun 2019 21:59:41 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/enhance-the-python-package-manager-to-handle-pip/idi-p/934556</guid>
      <dc:creator>TracyThorleifson</dc:creator>
      <dc:date>2019-06-11T21:59:41Z</dc:date>
    </item>
  </channel>
</rss>

