Bug ID Number |
BUG-000118430 |
Submitted | November 28, 2018 |
Last Modified | December 9, 2024 |
Applies to | ArcGIS Pro |
Version found | 2.2.3 |
Operating System | Windows OS |
Operating System Version | 10.0 64 Bit |
Status | In Product Plan
The issue has been added to the development team's backlog. The goal for issues with this status is to address them in a near-term release (next release or two). Check the issue's Additional Information or Alternate Solution section to see if there is helpful information until it can be fully addressed.
|
Workaround
Create the desired Python environment on a different machine that is connected to the internet. Zip this environment up and physically move it to the disconnected computer. Place the unzipped Python environment in one of the two recognized locations for Python environments (ex: C:\Users\[user]\AppData\Local\ESRI\conda\envs\) and ArcGIS Pro picks it up.
Another way around this issue is essentially cloning the base arcgispro-py3 environment:
- Navigate to where the default Python project environment is located, it is listed in the Python Package Manager but is generally located at C:\Program Files\ArcGIS\Pro\bin\Python\envs
- Right click and copy the environment folder for arcgispro-py3.
- Paste this folder in the current location (administrator privileges required) or the other recognized environment folder located at C:\Users\<user>\AppData\Local\ESRI\conda\envs
- Change the name of this folder to the desired environment name.
- ArcGIS Pro picks this up as a Python environment.
Force installation from local files
https://support.esri.com/en-us/knowledge-base/how-to-clone-a-python-environment-offline-by-forcing-in-000030572
Steps to Reproduce