Bug-ID-Nummer |
BUG-000118430 |
Eingereicht | November 28, 2018 |
Zuletzt geändert | December 9, 2024 |
Gilt für | ArcGIS Pro |
Gefunden in Version | 2.2.3 |
Betriebssystem | Windows OS |
Betriebssystemversion | 10.0 64 Bit |
Status | In Product Plan
Das Problem wurde dem Backlog des Entwicklungsteams hinzugefügt. Bei Problemen mit diesem Status ist das Ziel, sie in einer der kommenden Versionen zu beheben (in der nächsten oder übernächsten Version). Bis zur vollständigen Problembehebung finden Sie hilfreiche Informationen in den Abschnitten "Zusätzliche Informationen" und "Alternative Lösung" des jeweiligen Problems.
|
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
Schritte zur Reproduzierung