topic Re: ArcGIS Pro 2.2.0 and Python Package Manager in ArcGIS Pro Questions

ArcGIS Pro 2.2.0 and Python Package Manager

MitchHolley1 — Wed, 27 Jun 2018 18:00:14 GMT

I updated to Pro 2.2.0 today and noticed the default python environment is now read-only. The previously downloaded packages I had were wiped out with the new update. I need to get the package, spyder, back into my environment. So, I cloned the arcgispro-py3 environment in order to make the install.

Notice that the window says, "Restart ArcGIS Pro for your environment changes to take effect."

So, I clicked 'Exit'.

After the program restarted, I no longer have a cloned environment to select.

Can someone please help?

Re: ArcGIS Pro 2.2.0 and Python Package Manager

DanPatterson_Retired — Wed, 27 Jun 2018 18:11:13 GMT

My Spyder and everything else I had installed was in the update and is functioning.

And yes, the new environment is locked for some reason

Kory Kramer‌ can you flag someone to find out why … and cloning is failing miserably based on the number of related posts.

Re: ArcGIS Pro 2.2.0 and Python Package Manager

James_Whitacre — Wed, 27 Jun 2018 18:17:54 GMT

Yes, this is critical! Spyder is essential. Maybe it should be added to the default install?

Thanks Mitch Holley‌ for starting this thread.

Re: ArcGIS Pro 2.2.0 and Python Package Manager

George_Thompson — Wed, 27 Jun 2018 18:40:55 GMT

Kory Kramer‌ I have a case opened with support on this. I am able to duplicate the behavior.

Re: ArcGIS Pro 2.2.0 and Python Package Manager

DanPatterson_Retired — Wed, 27 Jun 2018 18:44:41 GMT

Bizarre... maybe nothing of mine got 'toasted' was because I was on Beta 2.2. Nothing got removed when I moved from 2.1 to beta 2.2 and everything is in it's place now... except for the fact that the package manager is locked.

I have been using Spyder etc without incident since moving from beta 2.2 to the upgrade 2.2 yesterday

Re: ArcGIS Pro 2.2.0 and Python Package Manager

HåkonDreyer — Wed, 27 Jun 2018 21:24:35 GMT

Seems something is fundamentally wrong with the Conda environment. Did a clean install of Pro and experience the reported behavior from inside Pro, and even a simple create fails from cmd.

Re: ArcGIS Pro 2.2.0 and Python Package Manager

Richard_Stokes — Thu, 28 Jun 2018 02:51:14 GMT

I have the same issue, any suggestions or workarounds would be appreciated.

I can clone the base pro environment or create a new one, and even though they're listed using conda env list, Pro refuses to recognise them. The resulting folder structures look normal, and there isn't a competing Python install or program overriding the path.

Re: ArcGIS Pro 2.2.0 and Python Package Manager

MarcoBoeringa — Thu, 28 Jun 2018 08:09:05 GMT

@Hakon Dreyer,

Please note that I already discovered one bug related to path names in the interface of the package manager of Pro 2.2, that may or may not be the root cause of this issue. I posted that with screenshots in this thread:

https://community.esri.com/thread/217056-error-with-toolboxes-in-arcgis-pro-22#comment-781502

Notice how Pro omits the "_" underscore in the path of the "backup" of the Conda environment that Pro 2.2 creates upon install. I could definitely see a wrangled path causing more issues...

Re: ArcGIS Pro 2.2.0 and Python Package Manager

Andreas_ElmelundHass — Thu, 28 Jun 2018 10:11:01 GMT

Same issues occur in my update to ArcGIS Pro 2.2. Wipes out my previously installed packages and dependencies and leaves me with no possibility to clone the existing environment folder. After the update ArcGIS Pro keeps throwing away the path to the cloned environment. This tutorial is then of no use: The Python Package Manager—ArcPy Get Started | ArcGIS Desktop . It's nice to see that ESRI tries to improve their ArcGIS Pro software, just a shame that they mostly don't manage the updates very well and that there seems to be a high risk of updating their software. It's so enormously time-consuming:-(

Re: ArcGIS Pro 2.2.0 and Python Package Manager

MitchHolley1 — Thu, 28 Jun 2018 12:59:13 GMT

I suggest we wait on a comment/resolution/workaround from George Thompson‌ and Kory Kramer‌

Re: ArcGIS Pro 2.2.0 and Python Package Manager

MarcoBoeringa — Thu, 28 Jun 2018 13:51:04 GMT

I think some people at ESRI are working overtime right now... hope to see a fix in a 2.2.1 release soon.

Re: ArcGIS Pro 2.2.0 and Python Package Manager

James_Whitacre — Thu, 28 Jun 2018 14:10:15 GMT

I noticed that when a new env was created, not all the files from the default arcgispro-py3 env were copied over. Therefore I experimented with copying the default env folder directly. I think I found a workaround for getting ArcGIS Pro to recognize the env:

Copy and paste the default, read-only 'arcgispro-py3' env in 'C:\Program Files\ArcGIS\Pro\bin\Python\envs' to 'C:\Users\[username]\AppData\Local\ESRI\conda\envs'
Rename the folder to be unique (e.g. 'arcgispro-py3-username')
Right-click on the folder, click Properties, and uncheck Read-only (not sure if this is necessary, but I did it and it worked...it may still work if this step is skipped)
Open ArcGIS Pro, then Package Manager, and activate the env (Note that a new 'proenv.txt' file is added to the env folder. I am not sure what this does, but it lists the folder of the newly create env.)

However, I cannot seem to install the Spyder package (I haven't tried other packages), it seems stuck and won't finish the install. I am wondering if the issue I raised a few weeks ago could be causing issues: Why is Spyder 3.2.8 not working with ArcGIS API for Python 1.4.1? Note that the default env includes ArcGIS API for Python 1.4.1.

Any feedback or adjustments on this workaround is appreciated. Thanks.

Re: ArcGIS Pro 2.2.0 and Python Package Manager

George_Thompson — Thu, 28 Jun 2018 17:13:55 GMT

I just got a response from technical support and they are aware of the issue.

My recommendation if for anyone encountering this issue to contact Esri Technical Support and get attached to the defect(s) that apply.

BUG-000112192 - Unable to activate a new Project Environment using the Python Package Manager

BUG-000111732 - Failed to activate a newly created Python environment in ArcGIS Pro

Re: ArcGIS Pro 2.2.0 and Python Package Manager

MarcoBoeringa — Thu, 28 Jun 2018 17:40:24 GMT

Hi James,

Thanks for posting this. I can confirm your workaround seems to work. Once I manually copied and renamed the default 'arcgispro-py3' environment to my user profile, I could indeed install new packages and make the change of the environment stick in Pro, instead of being thrown back to the default environment.

So I can now finally get to work.

I did not remove the 'read-only' property of the folder by the way, just copied and attempted to install a new package in the copied environment. You are correct about the 'proenv.txt' being generated as well, I saw that too. I haven't tried to install the Spyder package by the way, I just need pyodbc for now.

Re: ArcGIS Pro 2.2.0 and Python Package Manager

James_Whitacre — Fri, 29 Jun 2018 13:26:29 GMT

Thanks Marco. I edited my response by crossing out the read-only step.

Re: ArcGIS Pro 2.2.0 and Python Package Manager

JoeBorgione — Fri, 29 Jun 2018 14:00:06 GMT

Following your suggestion I'm attached. Seems like a show stopper to me; hope the get it fixed pronto!

George Thompson‌

Re: ArcGIS Pro 2.2.0 and Python Package Manager

DanPatterson_Retired — Tue, 22 Jun 2021 08:30:12 GMT

Maybe if we can get this upvoted, we can have package management AND documentation access to associated packages as the same time.

https://community.esri.com/ideas/14817

A small patch thanks to Anon (for now) enables this instead of using conda and/or the package manager and/or in conjunction with it

Re: ArcGIS Pro 2.2.0 and Python Package Manager

DanPatterson_Retired — Tue, 03 Jul 2018 01:33:57 GMT

S.W on Beta 2.2 suggested a fix to the conda_api.py script that enabled Anaconda Navigator to be installed and useable. I implemented the fix and cloned the environment using it. About to test... but it is there without any other dance steps.

I am sure another solution for those that don't need Anaconda Navigator will be found.

Re: ArcGIS Pro 2.2.0 and Python Package Manager

JoshuaBixby — Wed, 04 Jul 2018 15:16:34 GMT

Glad to see the beta program is identifying these issues with new functionality and addressing them before release. Oh wait....

Re: ArcGIS Pro 2.2.0 and Python Package Manager

DanPatterson_Retired — Wed, 04 Jul 2018 18:00:19 GMT

just had to install through conda instead of the package manager in Beta... In fact, you can still do it now, there are no roadblocks to conda install anything... but it would be best to have a 'clone' around