Include Python Clone in Pro in the .x releases

[EricErtl]

Our team has been experiences issues cloning the default Python environment for every .x release (2.7, 2.8, etc.).  Each release we have to create a new clone and the last version we have been able to upgrade to was 2.7 after whitelisting the recommended URLs.

If the clone is included in the release it solves our problem as we will have an environment available to us to make changes to.

[WilliamBlake1]

that is a great idea!!

[SeanO_Brien4]

Totally agree, cloning is way too difficult

[JeffKropelnicki]

This is a great idea!!

[AileenVelasquez1]

yes! I'm surprised this isn't already a thing!

[KoryKramer]

Thank you for submitting this @EricErtl It sounds like a duplicate of https://community.esri.com/t5/arcgis-pro-ideas/update-cloned-python-environment-s-while-updating/idi... 

Could you please review that idea (that is In Product Plan) and let me know if that it the same as what you are requesting?  If so, we'll merge this.  Thanks

[EricErtl]

Thanks @KoryKramer for commenting.

That option would be great if there was no attempt to reach outward to https://conda.anaconda.org or https://repo.anaconda.com.  Do you know if that is the case?  My interest in including the clone in each release is so Pro/conda does not have to access external urls in order to update, clone, etc. 

The only way for us to access external urls is through a proxy server and that is what is giving us issues with 2.8/2.9.

[HannesZiegler]

Thank you for the additional details @EricErtl, the solution for your request is in the product plan and will be made available with a future release.

If you are here looking for upgrading cloned environments from a previous release to be compatible with your current release, see here instead.

[HannesZiegler]

Hello all, a quick update: We have plans to address this but are delayed due to technical complications.