Python clone not usable after upgrade

[RandyCasey]

I experienced this when upgrading to both 2.4 and to 2.4.1. Each time, after the upgrade, I was unable to use the cloned version of Python and had to delete the cloned directory and recreate it. Not a show stopper, but definitely a time sink . Is there a way to avoid this? I am asking because I will be rolling out 2.4.1 early next week to all of our staff and would like know if there is a work-a-round or simple solution I am missing.

[George_Thompson]

I would review this thread for more information on this; https://community.esri.com/message/868913-updated-from-23-to-24-and-now-previous-python-environments... 

[RandyCasey]

Thank you for the thread link. This still appears to be an ongoing bug. I will submit to support as such. Thanks again.

[DanPatterson_Retired]

Definitely this should be done behind the scene for the user if they aren't conda literate and esri wants to encourage clones for people that don't have admin privileges on their machines.

Also, bookmark Release notes for ArcGIS Pro 2.4—ArcGIS Pro | ArcGIS Desktop 

Assuming all that is fixed in Pro 2.4.1 is listed in the above link, then I would skip it unless something on the list is required by your organization.  Bug fixes are listed but there is no indication of package upgrades.   In that vein, you should also consult

https://anaconda.org/Esri/repo 

To see if anything major was exposed to the casual user.

[JoeBorgione]

So an 'upgrade' to 2.4.1 breaks clones too?  Sheesh.... 

[GabrielMarcus]

Ugh. I knew I should have looked at this forum before upgrading. 

[JoeBorgione]

Yeah....  I'm holding out for a full version upgrade like 2.5 or better 2.5.1 instead of the incremental ones....

[MichaelVolz]

Or maybe a better python setup so the clone wars can end?

[JoeBorgione]

Seems reasonable to me.... See https://community.esri.com/ideas/15429 ....