nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ArcGIS Pro 2.2.0 and Python Package Manager

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?

Najděte více příspěvků označených jako

Accepted answers

Deafening....

edited to add:

In an email from ESRI tech-support I'm told:

Thanks for reaching out. Development recently commented that BUG-000112192 is fixed in the current Beta ArcGIS Pro version. So, it looks like a fix will be pushed out in the next publicly available patch. I hope that we see this soon, but I unfortunately don't have a definitive time frame.

All comments

DanPatterson_Retired

Your potential update is quite significant. I have Spyder installed as my python IDE so that accounts for only a few of your upgrades and the ArcGIS accounts for some more.

/blogs/dan_patterson/2018/12/13/spyder

and some clone stuff

/blogs/dan_patterson/2018/12/28/clone

What are you using for python?

I wouldn't install via pip let conda manage things.

You could give it a go, but I would have the ArcGIS pro install *.exe or at least the *.msi and *.cab file on hand incase you have to do a complete reinstall

You might want to start a new thread if you have issues..

NicholeSalinger

results from running

conda install tensorflow --dry-run

conda install tensorflow --dry-run - capture 1 of 3

FOLLOWING PACKAGES will be UPDATED [continued]

conda install tensorflow --dry-run capture 3 of 3

NicholeSalinger

Yes, I activated my cloned environment. See screenshot below arcgispro managing environment screenshot

I also tried updating using conda - following tensoflow's online instructions (Install TensorFlow with pip | TensorFlow )

BUT

I have not tried your method. Will report back.

DanPatterson_Retired

did you switch into the environment? did you try conda ? a dry-run suggests that the changes are quite a lot, so make sure that it isn't going to break something in other packages

(arcgispro-py3) C:\arc_pro\bin\Python\envs\arcgispro-py3>conda install tensorflow --dry-run
Fetching package metadata .............
Solving package specifications: .

Package plan for installation in environment C:\arc_pro\bin\Python\envs\arcgispro-py3:

The following NEW packages will be INSTALLED:

    _tflow_select:       2.1.0-gpu
    absl-py:             0.7.0-py36_0
    astor:               0.7.1-py36_0
    cudatoolkit:         9.0-1
    cudnn:               7.3.1-cuda9.0_0
    gast:                0.2.2-py36_0
    grpcio:              1.16.1-py36h351948d_1
    keras-applications:  1.0.6-py36_0
    keras-preprocessing: 1.0.5-py36_0
    libprotobuf:         3.6.1-h7bd577a_0
    markdown:            3.0.1-py36_0
    protobuf:            3.6.1-py36h33f27b4_0
    tensorboard:         1.12.2-py36h33f27b4_0
    tensorflow:          1.12.0-gpu_py36ha5f9131_0
    tensorflow-base:     1.12.0-gpu_py36h6e53903_0
    termcolor:           1.1.0-py36_1
    werkzeug:            0.14.1-py36_0

The following packages will be UPDATED:

    cffi:                1.11.5-py36h74b6da3_1     --> 1.12.1-py36h7a1dbc1_0
    ipython:             7.2.0-py36h39e3cac_0      --> 7.3.0-py36h39e3cac_0
    jedi:                0.13.2-py36_0             --> 0.13.3-py36_0
    keyring:             17.1.1-py36_0             --> 18.0.0-py36_0
    markupsafe:          1.1.0-py36he774522_0      --> 1.1.1-py36he774522_0
    openpyxl:            2.5.14-py_0               --> 2.6.0-py36_0
    openssl:             1.1.1a-he774522_0         --> 1.1.1b-he774522_0
    parso:               0.3.2-py36_0              --> 0.3.4-py36_0
    pip:                 19.0.1-py36_0             --> 19.0.3-py36_0
    pluggy:              0.8.1-py36_0              --> 0.9.0-py36_0
    prompt_toolkit:      2.0.8-py_0                --> 2.0.9-py36_0
    py:                  1.7.0-py36_0              --> 1.8.0-py36_0
    pytest:              4.2.0-py36_0              --> 4.3.0-py36_0
    python-dateutil:     2.7.5-py36_0              --> 2.8.0-py36_0
    pyzmq:               17.1.2-py36ha925a31_2     --> 18.0.0-py36ha925a31_0
    setuptools:          40.7.3-py36_0             --> 40.8.0-py36_0
    wheel:               0.32.3-py36_0             --> 0.33.1-py36_0
    win_inet_pton:       1.0.1-py36_1              --> 1.1.0-py36_0‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

NicholeSalinger

David Martinez‌ Alberto Nieto‌

I finally got approval to install tensorflow but running into an install issue with cloning the environment using the Python Package Manager. Finally just copied and pasted the environment as stated in this thread but running into issues updating and installing packages. Please advise. #tensorflowarcgispro-py3 python package manager‌

Thanks!... worked for me. Was about to tear my hair out trying to install the utilsolutions package

Thank you, Marco. Tried all the other suggestions and nothing worked.

DanPatterson_Retired

And conda installs can be made fun as well

/blogs/dan_patterson/2018/10/08/making-conda-package-installs-easier

Cloning doesn't actually "clone" your installation. It clones the packages in your installation. To accomplish the clone it downloads all of the packages from online repos as if you were creating a new installation for the first time. So when you don't let if finish out it won't be a complete environment.

Conda everything. ArcGIS Package Manager is not yet up to the task of managing Python environments. It'll get there some day I'm sure but it's not there yet.

Dan Patterson is on the mark. I've set up .bat files which allow me to automate 'cloning' my setup to each of my advanced users machines including Spyder, Anaconda Navigator, and Jupyter Lab while preserving the default ArcGISPro environment in case of a failure or revert or new clone for integration with R etc, requirement.

Or, if you want simplicity and to keep your hard drive from filling up with utterly useless clones, Conda straight into arcgispro-py3. Add Spyder and upgrade the ESRI packages to 1.5 and off you go...If I didn't have users with unique needs that's what I would chose to do.

deactivated-user-ChrisBeaudett

Thanks Joshua. I've let the dialog run to completion as well, but still no cloned environment after a restart.

I have gotten cloning to work, somewhat. For reasons I don't understand, I have to let the cloning dialog sit for 15-20 minutes while it works very slowly in the background to create the new cloned environment. If I close out of the dialog early, the environment is only partially created and doesn't work. Since I have a respectable machine with SSD drives, I can't explain why the cloning is so slow.

DanPatterson_Retired

I use Pro 2.2.3 with python 3.6 and Spyder

/blogs/dan_patterson/2018/07/01/arcgis-pro-your-conda-environments

/blogs/dan_patterson/2018/01/28/spyder

The caveat... The package manager no longer does anything, you have to do a conda install.

Which means you have to have admin rights of some kind to your computer.

If properly installed, Use file explorer and check for the existence of

C:\...Your Install Folder ...\bin\Python\envs\arcgispro-py3\Lib\site-packages\spyder

Plus some other spyder related folders.

If you want to make shortcuts for your desktop, it can be done..

Spyder isn't the only package that is distributed within Pro. If you want the 2.2 tactic reverted...

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

otherwise you will have to continue to fill up your system with clones, if you can get them to work

deactivated-user-ChrisBeaudett

I have Pro 2.2.3 and I'm seeing the same behavior when attempting to clone an existing environment: the new env just disappears. What's even more frustrating is that it's essentially impossible to get both the arcgis SDK for Python and ArcPy configured in a standalone conda environment w/ Python 3.6+ outside of Pro. So if you want arcgis + arcpy + any custom modules, you can't do it. And, Spyder is also apparently no longer installed w/ Pro. At least, I can't find it. (I'd prefer to use PyCharm anyway, but I'll take any IDE that will let me code + debug in a custom Pro env).

If anyone has done this (custom env with arcgis + arcpy) as of Pro 2.2.3 with Python 3.6+, please let me know your secret sauce.

DanPatterson_Retired

I always ride with my head out the wind.. not much of a herd guy either

Can this be of help? https://community.esri.com/thread/220006-another-arcgis-pro-condapythonspyder-post

Howdy Dan - I appreciate you sharing your alternate approaches and workarounds. At some point, I'm probably going to need to use them.

I'm attempting to stay onboard the Esri train, but I keep falling out windows, through the floors, etc.. I learned a long time ago to keep my arms and legs inside the ride at all times, if possible, so the support team doesn't have a clean "unsupported workflow or configuration" case closure response.

My actions:

submitted a support request, primarily as a "me too" indicator
searched "Edit with IDLE (ArcGIS Pro)" in my registry, found the key, copied the value (the entire string), went to ArcGIS Pro > Project > Options > Geoprocessing > Script Editor - pasted that thar string in that thar field > OK.
Now in ArcGIS Pro, I can right-click a script tool > Edit > and up it pops in an IDE instead of Notepad.
put any sort of Spyder goodness on hold until... sometime later.

Now I just have to figure out what it was I was doing for work and get restarted on that. Because that's what I'm getting paid to do instead of cobbling together tools.

tim

DanPatterson_Retired

Tim...

conda install or the clone

But you are probably in an environment where you can't without permissions,

For those not familiar with Spyder

/blogs/dan_patterson/2018/01/28/spyder …..

/blogs/dan_patterson/2018/07/01/arcgis-pro-your-conda-environments …. plus other options

So get onboard Tim

Install Spyder, Jupyter console and Jupyter notebook for ArcGIS Pro by default

Nice. My solution space is so constrained with Esri-tech by three walls: bugs, licensing, and strategy. I just bloodied my face on the bug wall again. ArcGIS Pro 2.2.2, hours burned, no Spyder.

DanPatterson_Retired

The 2.2.2 patch information only covers bug fixes.

Where is the information on

enhancements?
changes to the python modules
1. were new ones installed?
2. which packages were updated
are previous updates to the main installed wiped out?
you have to update the main install, then reclone it (see 3 above)
….. please add here

Logged a support request specifically for things breaking in appdata. Back to 2.1

DanPatterson_Retired

As said earlier... the solution to the clone wars is....

just saying …. Install Spyder, Jupyter console and Jupyter notebook for ArcGIS Pro by default

After several install/deinstall/reinstall scenarios I was able to get Spyder to function from the appdata directory. It seems that there is something very much not quite right with the ArcGIS Pro package manager:

When running a clone from the gui it downloads all of the packages from the internet - what????
- My cloned environments became unusable because of incomplete and corrupted downloads when cloning from the gui.
- One scenario my cloned environment completed with just 4.7 mb of files in it.
Conversely when running a clone from the command line it creates an actual clone of the ArcGIS pro environment and not a new download.
When installing spyder from the command line I could not get a good install in my appdata folder for reasons unknown.
Conversely when installing spyder from the gui into the appdata folder, it installed correctly and now works. I'm completely unsure what the difference is. Command line install of spyder worked fine in my test environment at c:\python3

Next - attempting a Anaconda Navigator install.

Update - Pros conda environment is still broken in regards to Anaconda Navigator in my install. Same exact errors as before upon initialization.

May I suggest that the ESRI team start with a base working install of Conda then add ArcGIS functionality into it instead of working backwards from ArcGIS to Conda. Pros Conda does not seem to maintain compatibility with the community standard.

If we could please have a working Conda environment we'd be a lot more apt to use Pro. As it is now, I can't recommend this software to any of the users in my Enterprise and I certainly can't support it if they do decide they want to use it. Thanks.

Update 2 - After a computer reboot Spyder no longer works from "AppData". Still works fine from c:\python\envs\myEnvName test location.

Got Spyder installed through package manager but there are Kernel errors just like before. It's the expected result.

Something in the security policy locks the users appdata directory from executing certain commands and files (.css for instance). Spyder will not function from within it. Nor will ArcGIS Pros environment.

Spyder is working fine for us when run from an ArcGIS Pro clone environment placed on the root c:\python3\envs\myEnvName

This is a flaw in the software design, not in the actual software itself.

Pro is useless to our municipality until ESRI fixes this and provides an environment install location that is not in the users AppData directory.

I have a need to run administration remotely and can not be calling python from individual local users app directories. That would be a scripting nightmare, especially when running the same scripts on different machines. For our network we require scripting environments that are identical on multiple machines as we have no desire to write separate scripts for each user on the network in order to undertake machine level processes.

It's fine if each user has the ability to create and use their own environments but the root scripting environment for the main software deployment needs to be accessible for us to add packages to when necessary as ArcGIS default install does not come with packages critical to our workflow like Spyder installed.

Maybe ESRI can consider a snapshot approach to environment management (refresh to install state) at the root for disaster recovery instead of forcing environments for each user when our needs are much simpler than that in the enterprise. Or maybe ESRI can set it read only be default but provide a switch that would allow us to change it if we desire.

Followed the above command line workflow to create and activate an environment in a local folder c:\python3\envs\myEnvName. With the command prompt still open, started Python 2.2.2. Went to Python Package Manager environment manager and my new environment was listed. Clicked the button to enable it as my project environment. Success! Even noticed a new Jupyter Notebook shortcut showed up for the new environment.

Then closed Pro and the command prompt and reopened them. My environment was no longer listed in the environment manager. It disappeared. Can't get it to come back. Tried recreating the environment but no joy.

As far as the "Update Package" issues, they still exist for me after creating a clone in my local user directory. 39 packages that can't be updated through the gui. Updating them at the command line works.

Hi I clone the original enviroment from the prompt (conda create -n -my_arcgispro-py3 --clone "YOURPATH"

Them I activate the enviroment (activate my_arcgispro-py3)

Them I updated the packages conda upgrade -c esri arcgis

Them I started ArcGisPRO 2.2.

I checked in PYTHON PACKAGE MANAGER and the MyEnviroment WAS THERE AND RUNING!!

Check here to see some tips also: Install and set up | ArcGIS for Developers

Allow us the option at least of deciding for ourselves what to install and where...

^^^^ This... ^^^^^

DanPatterson_Retired

PS... as for noise... that is a matter of opinion... there are lots of 'fluff' packages installed in the distribution already

DanPatterson_Retired

FYI... there is more than one Jupyter.... this is one, that I am referring to.

If I wanted to see a map (aka Jupyter Notebook), I would use ArcGIS Pro instead

AND

A cloned environment is totally useless in some environments... like teaching... where the Users folder is routinely wiped clean.

Our only option is to install the "pristine" environment using conda.

Allow us the option at least of deciding for ourselves what to install and where...

After all we are the users and those packages are part of the distribution, so I assume that they have been tested... everything worked in Beta 2.2 after I 'conda-ed' it... did something happen since then?

Emphasis on: ...as long as the Environment manager works...

Well, Jupyter is there by default already, and for us preferring a different IDE, shipping the default with Spyder will just be noise. But Spyder could of course be an option when installing.

IMHO keeping the default read only and support cloned environments is a good approach as long as the Environment manager works.

DanPatterson_Retired

just saying …. https://community.esri.com/ideas/15429

Just tried this workaround and it worked fine. Thanks!

I'll defer to Dan Patterson‌ ; I've purposely been waiting for an ESRI 'fix' so I don't have to deal with the conda clone approach.

I got the clone thing to work after understanding the new read only implementation and uninstalling Pro and any trace of Anaconda, etc. However even now, when I see the list of packages that have updates in the package manager and try to apply any of them - my conda_debug.log shows:

DEBUG:__main__:conda.cli.main called with ('C:\\Program Files\\ArcGIS\\Pro\\bin\\Python\\Scripts\\conda.exe', 'update', '--all', '-p', 'C:\\Users\\maugust\\AppData\\Local\\ESRI\\conda\\envs\\arcgispro-py3-MSA', '--json')
DEBUG:__main__:Ignoring first argument (C:\Program Files\ArcGIS\Pro\bin\Python\Scripts\conda.exe), as it is not a subcommand
INFO:conda.proconfig:proreg call
INFO:conda.proconfig:hive call
INFO:conda.proconfig:Detected ArcGISPro as product
INFO:conda.proconfig:proreg call
INFO:conda.proconfig:hive call
INFO:conda.proconfig:Detected ArcGISPro as product
DEBUG:__main__:conda.cli.main called with ('C:\\Program Files\\ArcGIS\\Pro\\bin\\Python\\Scripts\\conda.exe', 'update', 'python', '-p', 'C:\\Users\\maugust\\AppData\\Local\\ESRI\\conda\\envs\\arcgispro-py3-MSA', '--json')
DEBUG:__main__:Ignoring first argument (C:\Program Files\ArcGIS\Pro\bin\Python\Scripts\conda.exe), as it is not a subcommand

"DEBUG:__main__:Ignoring first argument (C:\Program Files\ArcGIS\Pro\bin\Python\Scripts\conda.exe), as it is not a subcommand"

Do I have something configured wrong here, or is this a bug? None of my available updates get applied and this appears to be why...

Just saw this on the above link:

How long are we talking, 2 minutes or 60 minutes?

see: https://community.esri.com/community/events/user-conference/blog/2018/07/10/esri-uc-day-2-updates

DanPatterson_Retired

To follow up on Logan's … when you clone from conda, you can actually see what is going on so you won't shut it down early

Not sure if it's been mentioned but cloning via the interface in Pro does work if you give it enough time. It seems to let you exit the interface prematurely, resulting in an incomplete clone. But if you wait it works just fine. I assume that is part of the bug.

DanPatterson_Retired

I had to install spyder during beta... no problems... I also installed jupyter console and jupyter notebook and a bunch of other things. No 'pinned' issues.

When Pro 2.2 (non-Beta) rolled out, I got to practice doing it all over again... this time it took me all of 5 non-waiting minutes to get it done.

I have been working all along as people wait until a 'fix' is made to the cloning. Unless you are way out there in terms of python modules, anything in the Anaconda suite is pretty safe. If things go 'south', conda is pretty smooth about removing stuff.

So in short... until they install spyder, jupyter console and jupyter notebook by default... you can either wait until someone else fixes stuff, or install your IDE now.

The worse case scenario?? What is your? I have none

Dan - can you talk to me like I'm 6 here for a second, hah - even if I can install packages directly thru conda, thus circumventing the package manager -- isn't the default environment "read only" now (2.2) for a reason? Would modifying it result in problems down the road?

@Hakon, i got by your problem by using `conda clean`. We're finding that some machines upgraded from 2.1 require this step.

Also, your use of `conda create` will create an environment without modules such as numpy, matplotlib, and arcgis (to name a few) which parts of arcpy needs. To create an environment that'll work with arcpy (and that you can use with ArcGIS Pro you should clone arcgispro-py3 like so

conda create --clone arcgispro-py3 --name %LocalAppData%\ESRI\conda\envs\my_env --verbose

Fixing the "CondaError: Cannot link a source that does not exist." error.

(arcgispro-py3) C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3>conda create --name prodebug2 python=3.6
WARNING: A space was detected in your requested environment path
'C:\Program Files\ArcGIS\Pro\bin\Python\envs\prodebug2'
Spaces in paths can sometimes be problematic.

Fetching package metadata ...............
Solving package specifications: .

Package plan for installation in environment C:\Program Files\ArcGIS\Pro\bin\Python\envs\prodebug2:

The following NEW packages will be INSTALLED:

&nbsp;&nbsp;&nbsp; certifi:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2018.4.16-py36_0
&nbsp;&nbsp;&nbsp; pip:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 10.0.1-py36_0
&nbsp;&nbsp;&nbsp; python:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3.6.6-hea74fb7_0
&nbsp;&nbsp;&nbsp; setuptools:&nbsp;&nbsp;&nbsp;&nbsp; 39.2.0-py36_0
&nbsp;&nbsp;&nbsp; vc:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 14-h0510ff6_3
&nbsp;&nbsp;&nbsp; vs2015_runtime: 14.0.25420-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; esri
&nbsp;&nbsp;&nbsp; wheel:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0.31.1-py36_0
&nbsp;&nbsp;&nbsp; wincertstore:&nbsp;&nbsp; 0.2-py36h7fe50ca_0

Proceed (<Y>/n)? y

ERROR conda.core.link:_execute_actions(337): An error occurred while installing package 'defaults::python-3.6.6-hea74fb7_0'.
CondaError: Cannot link a source that does not exist. C:\Program Files\ArcGIS\Pro\bin\Python\pkgs\python-3.6.6-hea74fb7_0\Lib\__pycache__\__future__.cpython-36.pyc
Attempting to roll back.


CondaError: Cannot link a source that does not exist. C:\Program Files\ArcGIS\Pro\bin\Python\pkgs\python-3.6.6-hea74fb7_0\Lib\__pycache__\__future__.cpython-36.pyc



(arcgispro-py3) C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3>conda clean --all
Cache location: C:\Program Files\ArcGIS\Pro\bin\Python\pkgs
Will remove the following tarballs:

C:\Program Files\ArcGIS\Pro\bin\Python\pkgs
-------------------------------------------

--- SNIPPED OUT LONG LIST OF PACKAGES AND PROMPTS ---



(arcgispro-py3) C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3>conda create --name prodebug3 python=3.6
WARNING: A space was detected in your requested environment path
'C:\Program Files\ArcGIS\Pro\bin\Python\envs\prodebug3'
Spaces in paths can sometimes be problematic.

Fetching package metadata ...............
Solving package specifications: .

Package plan for installation in environment C:\Program Files\ArcGIS\Pro\bin\Python\envs\prodebug3:

The following NEW packages will be INSTALLED:

&nbsp;&nbsp;&nbsp; certifi:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2018.4.16-py36_0
&nbsp;&nbsp;&nbsp; pip:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 10.0.1-py36_0
&nbsp;&nbsp;&nbsp; python:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3.6.6-hea74fb7_0
&nbsp;&nbsp;&nbsp; setuptools:&nbsp;&nbsp;&nbsp;&nbsp; 39.2.0-py36_0
&nbsp;&nbsp;&nbsp; vc:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 14-h0510ff6_3
&nbsp;&nbsp;&nbsp; vs2015_runtime: 14.0.25420-0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; esri
&nbsp;&nbsp;&nbsp; wheel:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0.31.1-py36_0
&nbsp;&nbsp;&nbsp; wincertstore:&nbsp;&nbsp; 0.2-py36h7fe50ca_0

Proceed (<Y>/n)? y

vs2015_runtime 100% |###############################| Time: 0:00:00&nbsp;&nbsp; 2.38 MB/s
vc-14-h0510ff6 100% |###############################| Time: 0:00:00&nbsp;&nbsp; 0.00&nbsp; B/s
python-3.6.6-h 100% |###############################| Time: 0:00:02&nbsp;&nbsp; 9.62 MB/s
certifi-2018.4 100% |###############################| Time: 0:00:00&nbsp;&nbsp; 0.00&nbsp; B/s
wincertstore-0 100% |###############################| Time: 0:00:00 881.16 kB/s
setuptools-39. 100% |###############################| Time: 0:00:00&nbsp;&nbsp; 4.67 MB/s
wheel-0.31.1-p 100% |###############################| Time: 0:00:00&nbsp;&nbsp; 5.26 MB/s
pip-10.0.1-py3 100% |###############################| Time: 0:00:00&nbsp;&nbsp; 6.07 MB/s
#
# To activate this environment, use:
# > activate prodebug3
#
# To deactivate an active environment, use:
# > deactivate
#
# * for power-users using bash, you must source
#


(arcgispro-py3) C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3>activate prodebug3

(prodebug3) C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN></Y></Y>

DanPatterson_Retired

Isn't the silence around this exciting though!

I'm waiting for a fix.

DanPatterson_Retired

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

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

DanPatterson_Retired

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.

DanPatterson_Retired

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

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

George Thompson‌

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

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.

George_Thompson

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

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.

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

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

Andreas_ElmelundHass

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:-(

@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...

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.

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.

Error message

DanPatterson_Retired

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

George_Thompson

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

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

Thanks Mitch Holley‌ for starting this thread.

DanPatterson_Retired

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.

Připojte se k diskusi

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.