AnsweredAssumed Answered

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

Question asked by ibroad on Aug 2, 2019
Latest reply on Oct 24, 2019 by athackrahesri-southafrica-esridist

I was trying to figure out a different bug that I'm having issues with and I thought updating Pro might help, so I updated from 2.3 to 2.4.


Now, when I look at my previous Python environments they all state "Broken Environment. Cannot be activated."


Is this just what we should expect going forward - broken environments with every little update?



Is there documentation on this that I'm missing? Why are there no warnings about this when updating? Should we just stick with a version of Pro and not update?