topic Re: Updated from 2.3 to 2.4 and now previous Python environments state "Broken Environment. Cannot be activated." in ArcGIS Pro Questions

//

_____ — Wed, 26 May 2021 00:03:27 GMT

Re: Updated from 2.3 to 2.4 and now previous Python environments state "Broken Environment. Cannot be activated."

JoeBorgione — Fri, 02 Aug 2019 18:32:04 GMT

If you do a search here on geonet with 'python env' your're going to find out quickly that you are not alone. I'm guessing your graphic shows previously cloned envs... You'll need to re-clone them.

Re: Updated from 2.3 to 2.4 and now previous Python environments state "Broken Environment. Cannot be activated."

George_Thompson — Fri, 02 Aug 2019 18:43:16 GMT

I saw that on my update to ArcGIS Pro 2.4 and just re cloned and updated the ArcGIS API to the latest version.

It is much easier now that it used to be.

I always recommend updating to the latest version to take advantage of all the fixes.

Re: Updated from 2.3 to 2.4 and now previous Python environments state "Broken Environment. Cannot be activated."

AnnekeThackrah — Thu, 24 Oct 2019 13:01:32 GMT

Still have issue when upgrading from pro 2.4 tot 2.4.2

Re: Updated from 2.3 to 2.4 and now previous Python environments state "Broken Environment. Cannot be activated."

JoeHershman — Wed, 05 Aug 2020 15:58:37 GMT

How does esri not give a way to update the cloned env. The reason it was cloned was to make changes. Re-cloning is a pretty lousy solution as now one needs to recall all the changes. I just did upgrade to 2.6 and have this issue. Amazes me sometimes esri doesn't fix this stuff (although, been working with their software long enough to never be amazed)

Re: Updated from 2.3 to 2.4 and now previous Python environments state "Broken Environment. Cannot be activated."

JoeBorgione — Thu, 13 Aug 2020 19:27:26 GMT

I've adjusted my attitude somewhat, adopting the opinion that Joshua Bixby‌ stated a couple of weeks back that cloned python environments are disposable. That said, for some reason the 2.6 cloning process was a little more painful than others. Not sure why, but I'm glad it's behind me.

I sat in on a User Conference session called Python, the road ahead, and the cloning issue is on the ESRI radar. Here's a discussion I started after that session: https://community.esri.com/thread/256608-python-the-road-ahead