A dministrator privileges … or you know the IT peeps … or you have created a cloned environment.
My installation path : C:\arc_pro ….. everything beyond this point is the same
Your installation path : C:\........... ….. got it?
Table of contents
1 Follow the help topics:
2 Go back to step 1.
Really, it is good and should be read, especially the part about your computer being able to run the software
3 My Esri, My Organization, Downloads
If it is there, it will look like the following:
4 Installation steps for retentives
Now, don't hit the Run option! It is tempting, but there is Save and Save As. Save As will be used.
To prepare for this, you should have done the following (not!, I am guessing)
Where step 1 is the main installation folder you created and downloaded the *.exe (2), when you run the *.exe, you will get the folder in step 3, and run the *.msi and you get the rest of the stuff.
Because if things go really really bad, you will know where the ArcGISPro.msi file is, so when you have to do a complete uninstall, you can reinstall within a minute.
Simple... no remembering or letting Microsoft Parent decide where things should go
I do the conda thing... some legacy but relevant reading
Crank up conda through whatever means to run ...proenv.bat which sets everything up. What is show below is what happens when I created a shortcut (Dolly) and messed around with the python ide so it isn't as dark and gloomy as yours will be.
I needed the following to do the programming I need and I did it in the following order.
1 Update numpy
2 Downgrade sphinx to 1.8.5 (needed IF you document your scripts, otherwise the documentation will look horrible)
3 installed sphinx_rtd_theme Getting Started with Sphinx — Read the Docs 3.5.3 documentation
You can skip this step if you don't do documentation or produce reports, or use Markdown or reStructured Text (or know what I am talking about )
4 Install spyder
Never, never install without doing a test run first!
(arcgispro-py3) ….snip …. >conda install some_package --dry-run
Then examine what it is going to do. Sometimes, nothing 'bad' will happen, but you should at least make a copy what you are about to install. If things go bad, you can roll back through the 'revisions' to a previous state.
Revision History from this install
(arcgispro-py3) C:\arc_pro\bin\Python\envs\arcgispro-py3>conda list --revisions
2019-06-27 20:36:30 (rev 0) Fresh install of ArcGIS Pro 2.4 in this example
... huge snip ....
(arcgispro-py3) C:\arc_pro\bin\Python\envs\arcgispro-py3>conda install --revision 1 (change 1 to your revision)
Just remember to change directory into your conda environment (ie cd c:\arc_pro\bin\Python\envs\arcgispro-py3 in my example.
There are load of IPython line and cell magics that can be used with Spyder.
Summary of magic functions (from %lsmagic):
Available line magics:
%aimport %alias %alias_magic %autoawait %autocall %automagic %autoreload
%autosave %bookmark %cd %clear %cls %colors %conda %config %connect_info
%copy %ddir %debug %dhist %dirs %doctest_mode %echo %ed %edit %env %gui
%hist %history %killbgscripts %ldir %less %load %load_ext %loadpy %logoff
%logon %logstart %logstate %logstop %ls %lsmagic %macro %magic %matplotlib
%mkdir %more %notebook %page %pastebin %pdb %pdef %pdoc %pfile %pinfo
%pinfo2 %pip %popd %pprint %precision %prun %psearch %psource %pushd
%pwd %pycat %pylab %qtconsole %quickref %recall %rehashx %reload_ext %ren
%rep %rerun %reset %reset_selective %rmdir %run %save %sc %set_env %store
%sx %system %tb %time %timeit %unalias %unload_ext %varexp %who %who_ls
%whos %xdel %xmode
Available cell magics:
%%js %%latex %%markdown %%perl %%prun %%pypy %%python %%python2 %%python3
%%ruby %%script %%sh %%svg %%sx %%system %%time %%timeit %%writefile
Certainly enough command line stuff to reminisce about the days of 40 character displays and green crts
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.