Latest Contributions by ShaunWalbridge

OK, yes those entries for 10.6 are causing the problem -- you can see on sys.path that they precede the actual places you want to be finding Pro DLLs, which causes the crash. Can you report what the below reports? import glob import os import site print("PYTHONPATH: {}".format(os.environ.get("PYTHONPATH", "undefined"))) print("PYTHONHOME: {}".format(os.environ.get("PYTHONHOME", "undefined"))) for loc in site.getsitepackages():     for pth in glob.glob(os.path.join(loc, "*.pth")):         print(pth)         with open(pth, 'r') as f:             print(f.read()) ‍‍‍‍‍‍‍‍‍‍‍‍‍ That should help debug things. Thanks, Shaun ... View more

Sam, are you still suffering from this issue? Do you have a custom environment you're working with, or just the default arcgispro-py3 environment? There are numerous places that Python can be injected into the environment that aren't entirely obvious (system variables, registry keys, cross-linked .pth files) so debugging can be tricky. Can you reproduce this from a command line session of Pro via the Python Command Prompt session? I can give you some starting points before you jump on with support. ... View more

Hi Joe Borgione‌, these two bugs are solved in Pro 2.3: BUG-000107377: Editing a script in ArcGIS Pro with a script editor ..  BUG-000106898: Setting the default editor for Python scripts in Arc..  Thanks, Shaun ... View more

In addition to Dan's advice, there's also the ArcGIS API for Python which is included in Pro, and includes a direct conversion to pandas via the spatially enabled data frame: Introduction to the Spatially Enabled DataFrame | ArcGIS for Developers  You can also see this GIS.SE post with some details on conversion: arcpy - NumPyArrayToTable - RuntimeError: unsupported time units. use M8[us] - Geographic Information Systems Stack Exch…  ... View more

We don't have a public release of what we're working on for this yet, but it's definitely on our release roadmap. In Pro 2.3, you can link Pro to an external environment, which may be helpful for your needs. If you're just using a 32-bit Anaconda installation, Pro should be entirely separate since it's all 64-bit as is the conda environments it creates. If you're seeing cross-talk in Spyder between Pro and your Anaconda installation, could you share some details of what the error your seeing is and I can try to troubleshoot them? Cheers, Shaun ... View more

The issues related to this should be resolved in Pro 2.3, if you still see any issues with this let me know. Cheers, Shaun ... View more

Thomas, Sorry to hear that you hit this. In a variety of circumstances, there was a bug which prevented the user-selected IDE from being launched, or IDLE which is shipped with Pro. I believe you're enrolled in the EAP program, and the latest Pro 2.3 candidates should have resolved these issues. If you configure an IDE, it should be used everywhere, including when editing script validation code. If you don't have an IDE selected, it should default to IDLE for all Python scripts now. The other suggestions in this thread are also good, and if you have further issues with using an IDE of your choice (or the default IDLE), please let me know. Thanks, Shaun ... View more

Nice trick! I've always found the colors provided with GitHub - neilpa/cmd-colors-solarized: Solarized color settings for Windows command prompt  to be helpful, I use those on my machines. ... View more

That's right, the second argument is the path that you want the notebook server started up in, with the default being %USERPROFILE%. You can also optionally change the shortcut to point at a location if you use one spot frequently for all your notebooks. ... View more

ArcHook doesn't look to support Pro currently. With Pro 2.1 and later, you should be able to directly use Jupyter Notebooks from the ArcGIS program group, as its included out of the box. Alternatively, you can start Python Command Prompt and then run "jupyter notebook". ... View more

Justin, Glad you found a workable option. You should be able to install Anaconda Navigator and Spyder from an ArcGIS environment, but going the other way is also useful. We're working on further improvements to make this process smoother in the future, purely copying the files can have problems if there are hardcoded paths in the files, but if it works, I won't complain! Cheers, Shaun ... View more

Francisco, Dan gave you all the main details, and I think set you in the right direction already. Just to reiterate a few points: Pro does ship with a full miniconda installation, and many additional dependencies that we either use internally or find that many of our customers use (Pro 2.2 ships with 78 packages at last count). If you do need the full set of packages that the Anaconda distribution provides, you can install the "anaconda" metapackage from within the Python backstage of Pro, and it'll pull in the full distribution set (or do the same from the command line). Using just command line conda will have no ill effects on ArcGIS Pro, if you don't update the environment that's driving the Pro application, then the environments will act in full isolation. At this time, the ArcPy package itself isn't available as a separate package, so typically the starting point is to clone the base "arcgispro-py3" environment (which contains ArcPy), then modify from there so you remain consistent with the dependencies of Pro. That said, if you're in fully isolated environments not driving Pro, you can feel free to experiment which is one of the great advantages of conda. Pro is all 64-bit, and that's also the case for the conda installation (a single conda installation is either 32- or 64- bit). We don't currently support conda for the 10.x product, and have no immediate plans to do so. That said, there are third-party guides on how to get Anaconda talking to ArcGIS 10.x, such as this USGS site maintained by  Curtis Price‌: Using Anaconda modules from the ESRI python environment - USGS OEI/Enterprise GIS - myUSGS Confluence Cheers, Shaun ... View more

I've reached out to one of the Anaconda Navigator developers to see how / if we can submit patches to their upstream source, that's the best way to get this fixed in the long run. ... View more

Hello Dan, The issue here is how Anaconda Navigator attempts to start the underlying Python session. We can report this issue upstream to the Anaconda Navigator developers, and have them apply a fix, that's the best long term solution to this since the issue isn't something we can fix directly without permission from Anaconda. That said, I've cleaned up a patch and provided more clear steps on how to get an Pro + Navigator environment: Patch Anaconda Navigator to use conda executable instead of root python wrapper to conda · GitHub  If you'd like to see this fixed upstream, we should create an issue with Anaconda and we can follow up there. Cheers, Shaun ... View more