Latest Contributions by ShaunWalbridge

Brooks, The r-bridge-install toolbox that you ran to show the R Installation Details can be used to install the bridge -- that will make the package available in R without using `install.packages'. The package itself isn't on CRAN, and that's why the installation command doesn't work. The bridge should work fine with any version of R 3.1 or later. Cheers, Shaun ... View more

Hello Robert, It looks like there's a verified bug with conda for installing QT. The reported fix is to upgrade conda, you can install the latest version of conda with the command:   conda update conda Let us know if that fixes the issue for you. Cheers, Shaun ... View more

Filip, Sorry to hear you continue to have problems. It can be tricky to debug some of these issues, in part because we're probably using different versions of Conda and Python if you've upgraded. Do you get a crash dump, or any further details if you click "Debug the program"? ... View more

Filip, Sorry to hear you continue to have problems. It can be tricky to debug some of these issues, in part because we're probably using different versions of Conda and Python if you've upgraded. Do you get a crash dump, or any further details if you click "Debug the program"? ... View more

Hi Filip, Yes, it is normal to not be able to run spyder from a default command line prompt – we've intentionally sandboxed our Python installation and don't modify the PATH of the machine. If you do want to explicitly add the Python environment to your PATH, you can add the ArcGIS\bin\Python\envs\arcgispro-py3\Scripts directory to the path, and it should work like any other entry. Could you post the results of:   conda info On your machine? Also, you may want to try creating a new environment with just Spyder, and seeing if it works there – it adds a new shortcut under Anaconda 3 (64-bit) > Spyder (env-name) you can try opening. To create the environment, try something like this:   conda create --name spyder-test python=3.4 spyder If that doesn't work, that helps isolate it as a conda issue, since that environment should have no interaction with ArcGIS Pro. ... View more

See if the instructions Continuum provides for running Spyder help. Cheers, Shaun ... View more

Here's a script that downloads a full list of current Anaconda packages: GitHub - scw/anaconda-packages: Create an installable list of current Anaconda packages Running the anaconda-packages.py script will create a list of the currently installable packages, in this case in the anaconda-packages-py34.txt which is included for illustration. This list can then be installed from conda with:     conda install --file anaconda-packages-py34.txt Cheers, Shaun ... View more

Can you visit the URLs manually? https://conda.anaconda.org/esri/win-64/​ should resolve in most environments. Also, what version of Python are you installing into? Python 3.5? ... View more

Adding to Dan Patterson​'s answer, yes you can use conda to install xlswriter. To do so, you can open a new Python Command Prompt window from the "ArcGIS Pro" program group, then execute: conda install xlsxwriter As Dan mentioned, we do include xlwt which provides similar functionality as xlsxwriter , but having both as options is nice. Unlike the Anaconda distribution, we ship a minimal set of packages with ArcGIS Pro, to keep the install size down. Here's the list of included packages as shown by conda list : arcgispro            1.3 colorama             0.3.6 future               0.15.2 matplotlib           1.4.3 msvc_runtime         1.0.1 nose                 1.3.7 numpy                1.9.3 openssl              1.0.2h pandas               0.17.1 pip                  8.1.1 py                   1.4.31 pyparsing            2.1.1 pypdf2               1.25.1 pytest               2.9.1 python               3.4.4 python-dateutil      2.5.3 pytz                 2016.4 requests             2.9.1 scipy                0.16.1 setuptools           20.7.0 six                  1.10.0 sympy                0.7.6.1 vs2010_runtime       10.00.40219.1 wheel                0.29.0 xlrd                 0.9.4 xlwt                 1.0.0 ... View more

Hi Dan, Can you try pointing the script editor to the Spyder executable itself? For a default global install, that should be: C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\Scripts\spyder.exe I tried it out locally, and it at least worked here. At Pro 1.3, we no longer register ourselves as the default run handler for Python scripts, which may make a difference for how to configure this. Note that some editors are having issues (such as IDLE), and this may be related, there's currently a bug assigned to the issue (BUG-000097665). Cheers, Shaun ... View more

Can you use background geoprocessing? It's designed for this purpose, and if you install 64-bit background geoprocessing, will give you the advantage of providing a 64-bit environment (e.g. access to more memory, some performance improvements on a 64-bit machine). ... View more

Hi Dan Patterson, My understanding is that the standard installation locations are recommended in part because of how the Windows security model is set up – for example, Python at 3.5 similarly installs itself into Program Files as addressed in this bug​. That said, I'm not aware of any specific limitations you would hit by installing into another location, and have used and tested ArcGIS Pro 1.3 in other top-level locations for a global install. Hope that helps, Shaun ... View more