C lone or not to clone
NOTE: I will be updating with a new guide for ArcGIS Pro 2.4 when it is released (Beta 2 is now complete.
I will provide the link here.
Why Not Clone?
Result.... I couldn't install any packages through Pro's package manager, and when I installed Spyder via conda in my clone, it couldn't import arcpy
So far I have made upgrades to
Testing without installing
You can check the affect of package updates without actually installing them. I still recommend using this first, then check the list for possible conflicts issues. Launch conda, then ...
conda install <your package name> --dry-run
This is the dashed line... below is for cloning... the package installation is the same for both
Clone... If you have to do it, here is a guide. This guide is only for people which have actual control over their computers.
You can launch proenv.bat via your windows start options under the guise of the Python Command Prompt.
I prefer to make a desktop shortcut as shown below.
Your environments can be controlled within ArcGIS Pro's package manager or via 'conda' accessed through proenv.bat.
It is slower and you don't get a lot of information, but they are improving it as they go along. Activate the environment, close Pro, then restart with the new environment.
The shortcut brings up the command prompt in you active environment. To obtain information on your environments, just run conda info --envs
You can add a package from within the package manager of via conda. Since I prefer the --dry-run option in conda, I will illustrate it here. You can leave out the --dry-run option to perform the actual install once you are sure you won't cause any foreseen issues.
You can upgrade a package either from the package manager in ArcGIS Pro or via conda. The package manager seems to take longer and you don't get much feedback during the process.
Again, I prefer to examine an upgrade using the --dry-run option first, prior to committing.
Ok... love that blue? /blogs/dan_patterson/2018/10/08/making-conda-package-installs-easier
Now not everyone needs this nor can everyone do this, but with a patch on a single file, you can add an alternate package manager and access to a load of documentation links.
In order to get the above, you have to edit a few lines in the 'conda_api.py' which will located in your clone path
The patch given by
entails altering a couple of lines in the conda-api.py file. I made a copy of the original and made fixes to the other in case I needed to undo the changes quickly. Not ideal, but worth it if you need to provided documentation and application shortcuts to users with diverse computing backgrounds.
Like I said... you don't need it, but it is a definite 'nice'.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.