Note: ArcGIS Pro 3.1 must be installed prior to installing any ArcGIS Pro 3.1 patches. Patches are cumulative. When you install this patch, the issues addressed in a previously released patch are also included. It is not necessary to perform an incremental update of previous patches before installing this one. Here is additional information about Minor Releases and Patches
Hi @HayleyHume-Merry , yes, BUG-000157970 was fixed in 3.1.2. There was some confusion with labelling/linking of issues on our end about whether it should be included in the list. Thank you for pointing this out. The list is updated at -us/media/products/arcgis-pro-issues-addressed/arcgis-p....
so it seems that the conda update is not pulling everything down from the 2.1.0.3 update. I had to remove the cloned environment and then re-create it, but this time I did not run the conda update. Any suggestions?
-- no pin param, that again is an early holdover I used when the conda would not update because the arcgis api module was 'pinned'. I'd mark your reply as correct and give you a kudos but as this is a 'Document' post I don't have that option...
Hello, new user here. Have tried to apply this patch via ArcGIS Pro interface and alternately by downloading the .msp file from My Esri. On each occasion I receive the following message and the update fails.
The d: folder is shared with all users and I'm logged in as administrator. Wondering if the error might be due to installing ArcGIS on a non-standard drive (d: instead of c:)? Has anyone solved this issue?
I am trying to import arcpy in a script, which is running in a PyCharm environment using the Python 3.6.6 installation that comes bundled with ArcGIS Pro 2.3.2 as the base interpreter. I get the following error:
Based on the answers to Why can't I import arcpy? and other similar issues, I have opened that Python interpreter on the command line, ensured that I can import arcpy (which I can) and then checked sys.path, which gives me:
I have created a .pth file in venv\Lib\site-packages that contains all of these paths. Without this file, the error given was "no module named arcpy" and with only 'C:\Program Files\ArcGIS\Pro\Resources\ArcPy' on the list, the error was "no module named arcgisscripting". With the complete list above, the error is the one I give at the beginning of this question.
I found the answer - I found the .pth file located within the ArcGIS Pro installation itself (default location C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\Lib\site-packages\ArcGISPro.pth) and used it as the basis for the .pth file in my virtual environment, which now looks like this:
b1e95dc632