Latest Contributions by ShaunWalbridge

@SteveLewis Thanks for providing some additional context. It looks like this issue may be specific to your environment and require some debugging to determine the nature of the problem. Can you log a support ticket for this case? In the samples given the Python 2.7 environment is running against the Server installation, where the Python 3 environment is running against Pro. It may be that these are licensed differently, or it may be that xp_cmdshell launches these processes as a different user than the authenticated user, and the job needs to be set up to reflect the need to authenticate as the running Pro user. I did install SQL Server Management Studio SSMS, but didn't see anything related to xp_cmdshell built into that package, so imagine there are additional steps to recreate the specific configuration being used, and support is the best avenue to try and tease out where the licensing issue is being hit. ... View more

Thanks for the suggestion, Dan. We've discussed this, and think that the audience for a system to manage environments independent of our software would add more complexity than the value it would provide for most users warrants. Of course, you know the existing options for this problem but I will reiterate them here for any others who come across this idea: To have a rich UI for managing and creating arbitrary conda environments, Anaconda Navigator can be used. It can be installed via the Pro Package Manager or with conda install anaconda-navigator, then launched from its menu shortcut or by running anaconda-navigator from the command line. From the Python command prompt, conda create can be used to create environments with any packages in them, including different versions of Python or no Python at all. ... View more

I believe that you can work with libspatialite by installing it from conda-forge: conda install conda-forge::libspatialite sqlite3 sqlite> SELECT load_extension('mod_spatialite.dll'); I don't think we have any immediate plans to reconfigure how we deploy sqlite, so will mark this as implemented since it does work via conda, but we can think more about this if it continues to impact your work.  ... View more

Could you provide additional details or an example script of what you're trying to do which isn't possible with the openpyxl driver for pandas only? Looking over the class documentation it doesn't call out limitations of specific drivers, so it'd be helpful to have a case we can evaluate. Ideally we'd like to maintain one library for interacting with XLSX files — as the distribution increases in size, the complexity of managing it increases so we carefully evaluate additions. Thanks! ... View more

There will be some user education required to use a package of this type, as some GP tools will fail to execute without the full set of dependencies. That said,   agree this is worthwhile doing for advanced users using ArcPy outside the default environment. ... View more

Thank you for your contribution to the ideas site. At this time, we do not intend to change the method signatures for ArcPy functions, as the all lowercase name is typical for Python keyword arguments and modifying it at this time would break existing code with the current keyword usage. The env API was derived separately and uses mixed case names at the time of its development. A related change we did add at Pro 2.8 is the arcpy.env names will raise an error if passed a name not matching, e.g. arcpy.env.cellsize will raise. ... View more

The py.exe model works well for environments where there are two distinct Python installations on the machine (one Python 2 and one Python 3), and was an important step in the phased transition between the two versions of Python. In the case of our products, it doesn't sufficiently address the issues of binding to Python across multiple products:  - Multiple product offerings ship with Python 2.7, such as Desktop, Server, and Background Geoprocessing, all which have claim to the Python 2 slot  - Multiple product offerings ship with Python 3, such as Pro, Server and Drone2Map which all have claim to the Python 3 slot  - In the case of Python 3, users can create multiple environments with different requirements and dependencies. Conda doesn't include py.exe in part because the current implementation can introduce cross-environment issues of the kind that environments are designed to prevent. Conda environments require an activation step as they rely on modifying the PATH for the duration of the execution to allow siloed sets of modules and DLLs to co-exist That precludes us from using the py.exe approach as it stands, but we do want to ensure that all versions of Python can be correctly addressed. For Python 3, the active environment can be addressed by calling the propy.bat script for the particular product. With the next release of the 10.x products, we have also ensured there is a clear mapping for each offering to edit and run each separately: These values can also be found in the registry, and added to custom handlers to launch an appropriate environment for execution. I know that isn't specifically what you had asked, but hopefully that helps you move forward and feel free to follow up in this idea. Thanks, Shaun ... View more

Anaconda navigator has made changes to how it calls conda and now works out of the box. ... View more

ArcPy is available as a conda package, which supports the full set of dependencies. ... View more

Can you confirm this remains an issue for you? The sqlite provided in the Python environment has gone through multiple changes since you posted, and would appreciate your input if this is still impeding your work. ... View more