Latest Contributions by ShaunWalbridge

Hello Kevin, Could you provide some information on how you start PowerShell and whether you have any integration with e.g. Python.NET being used? When I start a new Windows Terminal session with Powershell, I can use the scripts and it seems to work without issue. I wouldn't expect to see .NET exceptions being raised from a Python perspective, so am not sure where these are entering into the picture. Cheers, Shaun ... View more

Pro includes a number of cryptographic packages, including a full OpenSSL installation if you want to work with that. Probably easiest is to use the `cryptography` package to make your calls: https://cryptography.io/en/latest/ It supports a wide range of cryptographic primitives and is heavily tested for security. You may be better served by switching to Fernet (https://cryptography.io/en/latest/fernet/) rather than working directly with AES, and if your only goal is to securely store credentials, I'd recommend instead looking at https://keyring.readthedocs.io/en/latest/index.html which is also included in Pro. Keyring lets you store the credentials directly in the Windows Credential store and access them there, which avoids multiple classes of issues in trying to manage your own cryptographic system. ... View more

I believe this issue was caused by recent changes that went into the Pro 3.1 release affecting custom environments. You can address them on a 3.0 machine (any version) by adding the `pro-notebook-hotfix` package to your environment which correctly pins the notebook dependencies. You can also fix this by upgrading to the recently released Pro 3.1 release, see more details here for how to fix the issue: https://community.esri.com/t5/python-documents/arcgis-notebooks-in-arcgis-pro-3-0-faq/ta-p/1196582 Cheers, Shaun ... View more

Yes, that's right, we needed to add a fix on our end to make this work. One of the challenges with conda and custom packages is, once you've released something you effectively can't take it back because it'll be installed and used, and if the dependencies aren't specified tightly, conda will always choose the version that is "easiest" for it to solve, which in this case involved bad dependencies. We've put the fix up which can be added to any custom environment by installing the `pro-notebook-hotfix` package. There are also details on how to do this in the first question of the Pro Notebooks 3.0 FAQ:   https://community.esri.com/t5/python-documents/arcgis-notebooks-in-arcgis-pro-3-0-faq/ta-p/1196582 If it is available to you, you can also upgrade to Pro 3.1 which works out of the box without needing to add any additional packages. Cheers, Shaun ... View more

We recently upgraded the Notebook stack provided on the Esri channel in preparation for the Pro 3.1 release, and think that this is causing the regression in custom environments. I've logged an issue for this and will update the thread once we have a solution available. Sorry for the trouble with custom environments. Cheers, Shaun ... View more

The 1.1 version of the package is targeting a newer release of R (4.1), and unfortunately that version isn't available in the default channels. Because 1.1 gets selected from the UI automatically, I've removed it from our channel for the time being until we sort out the R version problem. Thanks for reporting this, and let me know if you can install r-arcgis-essentials again. ... View more

Are you able to see if the same code works from a plain RGui 4.2.2 session independently of RStudio? Can you check for any crash dumps in %LOCALAPPDATA%\CrashDumps with names like "rsession*.dmp" and if any of those files exist, send one to me via private message? I can look at what the crash itself says. Finally, could you share what licensing mechanism you're using, and whether opening ArcGIS Pro itself is working OK? Thanks! ... View more

The caches that Pro maintains don't have any relationship with the caches that Python code uses, so you will be fine leaving those alone. The Python module import system is somewhat complicated, and I would do some investigating to see what is happening when you run your imports, when you run from subfolder import module it may not be importing what you are expecting it to import. Depending on how your sys.path is configured. You might check that just after you run that import line what the value of these variables are: import sys print(f"sys.path entries: {sys.path}") print(f"path of imported module: {module.__file__}") If the path of the imported module is your other copy, then you've found why what you're loading differs from your expectations. You have a few options to sync these up, perhaps the simplest is to use sys.path.insert(0, 'path-to-thing-you-want') in your code to prepend the path to the custom object. You may also be better served using the Python tooling for working with packages and make this a package depending on how complicated your deployment is for this. If this is only local, you could also have the dev and release builds use different names to ensure clarity. Cheers, Shaun ... View more

Try starting a Python Command Prompt session, then run `python -v` and import your script from that environment. You should be able to see every import that is performed, and identify if your code is coming from some other location than where you expected based on the Python import path. Or please share some of your code so we can see what might be the cause. Cheers, Shaun ... View more

Thank you for your contribution. The Python Add-in interface isn't receiving enhancements based on ArcMap's mature status in the product lifecycle. Future development is going into the Python developer experience in ArcGIS Pro and our other product offerings. ... View more

With Pro 2.9, ArcGIS Pro was updated to GDAL 3.3.0, and Pro 3.0 ships with GDAL 3.4.0. We can't easily allow free-floating upgrades of GDAL because of its significant use elsewhere in the software, but we continue to upgrade it and make the version Pro includes close to the latest available upstream. Thanks for your idea! ... View more