The ArcGIS API for Python is a fantastic implementation but there are some places where it doesn't fill the gap.
Examples of these include creating scripts for use in toolboxes or chained and complex workflows.
Use case referenced in this instance is a chained GIS workflow that is basically its own custom software application implementation which manipulates GIS features across a multi-database and multi-file store ecosystem resulting in a new data product that has to meet rigid controls for integration into a 3'rd party web application with a data package that gets deployed to testing and prod GIS server environments.
The REST API part of that process is very minimal but extremely crucial component - which we are still trying to update from Py 2.7 to Py 3.6 so we can completely end our use of ArcMap and Py 2.7.
What we really want to avoid is having to code some parts of the process in different Pythonic environments or in combinations of multiple languages.
What brought about my post on this thread is that we would very much like to have Jupyter Labs and Spyder working with the ArcGIS Pro environment as a super great and elegant solution for this particular application development need but are stumped because while we were able to work with them in Pro 2.5, we are among those that are struggling for success in 2.6
Presently using a combination of PyCharm and VSSCode to work with Pros Py 3.6.10 environment.
Would love for a unified approach to the foundational Pythonic components of the ESRI ecosystem (especially since Py 2.7 and Py 3.6 are incompatible and as Dan notes some 3.6 components are already retiring) and really see that as something very important to both successful adoption of the tools ESRI provides to the user base and strong user support for the ESRI products moving forward.
