idea update cloned python environment(s) while updating arcgis pro in ArcGIS Pro Ideas

update cloned python environment(s) while updating arcgis pro

Mascht — Mon, 19 Aug 2019 21:17:35 GMT

Hi esri folks,

thank you very much for including a python package manager into ArcGIS Pro!

Unfortunately, my installed packages have got lost just by every update of Pro since then, because cloned python environments haven't been taken into account during the update process...

Happy GISing,

Mascht

Re: update cloned python environment(s) while updating arcgis pro

JoeBorgione — Mon, 19 Aug 2019 21:59:45 GMT

ESRI: Pretty please with a cherry on top?

Re: update cloned python environment(s) while updating arcgis pro

ScottBridwell — Mon, 19 Aug 2019 23:40:24 GMT

Yes, this should be a high priority item.We shouldn't have to re-create our environments every time a patch is released.

It would also be nice to make it easier to access arcpy from an external anaconda environment.

Re: update cloned python environment(s) while updating arcgis pro

MichaelVolz — Mon, 26 Aug 2019 21:35:57 GMT

Could not agree more!!!!

Re: update cloned python environment(s) while updating arcgis pro

Anonymous User — Thu, 12 Mar 2020 14:42:40 GMT

I can understand that each new version of PRO requires different packages and updating the main software overwrites the default the environment, however it shouldn't invalidate the cloned environments and require us to recreate them each time an update comes our way. Maybe it should create backups of the cloned environments and then go through the clones and update those packages that have been updated with the main env so they are not invalidated.

Another idea is to create yml of the environments so we can recreate it more easily than waiting for PRO to clone the environment, search for the packages that we had and install/update them. And since we cannot rename the environments, we have to do it in order so that PRO's naming convention names the environments (clone1, clone2, clone25 etc.) so we don't have to reset the interpreters env's we have set up in our IDE's. There is a lot of space in the python manager window- including a section that can install an environment from a yml would be useful.

Re: update cloned python environment(s) while updating arcgis pro

AdamBakiera — Wed, 31 Mar 2021 13:19:18 GMT

This would definitely be a very nice feature. We had all sorts of issues when we upgraded from 2.5 to 2.7. So for others that have experienced these issues, do you get them when you install patches too? There is a 2.7.2 patch available but if we have to re-create Python environments, it makes it a much longer process. Thanks!

Re: update cloned python environment(s) while updating arcgis pro - Status changed to: In Product Plan

ShaunWalbridge — Sat, 14 Aug 2021 03:31:42 GMT

We hear you! Providing a tool to upgrade Python environments is in the product plan and will be addressed in a future Pro release.

Re: update cloned python environment(s) while updating arcgis pro

Mascht — Tue, 05 Apr 2022 22:08:38 GMT

I hear you! Great to know that!

Happy GISing
Mascht

Re: update cloned python environment(s) while updating arcgis pro - Status changed to: Implemented

KoryKramer — Fri, 24 Jun 2022 14:57:16 GMT

This option has been added in ArcGIS Pro 3.0. See to see this and all of the other ideas you can look forward to when you upgrade.

Also be sure to check out the What's New documentation: https://pro.arcgis.com/en/pro-app/latest/get-started/whats-new-in-arcgis-pro.htm

Re: update cloned python environment(s) while updating arcgis pro

Anonymous User — Wed, 06 Jul 2022 13:17:07 GMT

Thank you @KoryKramer / esri!

Re: update cloned python environment(s) while updating arcgis pro

KoryKramer — Wed, 06 Jul 2022 14:21:52 GMT

I'll be sure to pass your thanks on to the team @Anonymous User

Re: update cloned python environment(s) while updating arcgis pro

Mascht — Wed, 13 Jul 2022 20:16:31 GMT

High Esri folks,

many thanks to everybody involved in implementing my Idea. Worked nicely after updating Pro to 3.0.

Happy GISing,
Mascht

Re: update cloned python environment(s) while updating arcgis pro

FakeName — Wed, 29 Nov 2023 09:42:08 GMT

Definitely didn't work when I updated from 3.1.x to 3.2.0. The "update" simply deleted the clone after about 10 minutes 😞

Re: update cloned python environment(s) while updating arcgis pro

ShaunWalbridge — Thu, 30 Nov 2023 03:28:56 GMT

@FakeName I took a look at this, and I think I've identified what the issue is. If you have any existing resources open that reference the environment directory, it will currently cause a failure. So for example, if you have a command line prompt at the working directory of the environment, that will lock the location and Windows won't be able to delete the folder. There is a second bug which is that the restore doesn't happen in this case either. I have local fixes for these issues and will look to get them into software, for now, here's a workaround:

1. Your environment doesn't get deleted, it is archived first. If you navigate to %LOCALAPPDATA%\Esri\conda\envs, you should see a file called <env name>.tar.bz2. This is a conda-pack archive of your environment, you can extract it with current builds of Windows 11, 7-zip or by using conda pack to restore your old environment from Pro 3.1.

2. Once you have that in hand, from the Package Manager interface of Pro you can add the environment back to the environment list. If you do this, then ensure that no other resources are referencing that environment, the upgrade should work as expected.

Sorry for the trouble and will look to fix this soon.
Cheers, Shaun

Re: update cloned python environment(s) while updating arcgis pro

JTessier — Thu, 21 Nov 2024 21:54:23 GMT

@ShaunWalbridge is this a bug you are tracking? If so what product version do you see it for? We struggle mightily with the python clones everytime we upgrade Pro.

Thanks!

Re: update cloned python environment(s) while updating arcgis pro

ShaunWalbridge — Thu, 21 Nov 2024 22:07:02 GMT

@JTessier the specific issue that @FakeName identified was fixed in Pro 3.3, which is if you had active things running against the environment that you're trying to upgrade it wouldn't correctly get upgraded and just leave you with the backup. It will now in that case fully restore the environment back to its original state, and the upgrade should work once those file handles are unlocked first.

If you see specific issues with upgrading your custom environments, can you share details on what the failures are, and what kinds of packages are present in your environments?

Re: update cloned python environment(s) while updating arcgis pro

JTessier — Thu, 21 Nov 2024 22:25:04 GMT

Thanks Shaun, will do, we are just in process of upgrading Pro to 3.3 and noticing that our python scripts silently stopped working and determined the python clones were not upgraded along with the default clone. More to come, but hoping the next upgrade goes smoother.

Re: update cloned python environment(s) while updating arcgis pro

ShaunWalbridge — Fri, 22 Nov 2024 04:37:34 GMT

@JTessier Got it. Custom environments can't be directly upgraded by the software upgrade process, because they weren't created by it (MSI files specify the files they have written, and those are the things they can change). To upgrade custom environments, follow the instructions provided here: https://pro.arcgis.com/en/pro-app/latest/arcpy/get-started/upgrade-an-environment.htm

In most cases, it should be as simple as clicking the upgrade button within the UI, but it is possible to invoke from the command line or with a script as well. This process should migrate both custom installed conda and pip packages.

Re: update cloned python environment(s) while updating arcgis pro

dbKlingdom — Fri, 22 Nov 2024 16:02:20 GMT

Hello, During our last upgrade of Pro to 3.3.1 we had to use the UI in Pro to upgrade the Clone However this Process created a new Clone-1, which is not ideal. We would like to have only the one Clone.

Re: update cloned python environment(s) while updating arcgis pro

JTessier — Fri, 22 Nov 2024 17:17:46 GMT

Agree with @dbKlingdom above.