topic Re: Clone python environment on shared drive for multiple users to access in ArcGIS Pro Questions

Clone python environment on shared drive for multiple users to access

LouEarly — Thu, 18 Jan 2024 15:26:59 GMT

Is there a way to clone a python environment to a shared drive so that multiple users can access it through pro?

We are using VDI's for a large number of editors and would like them to all be able access the same tools without having to do individual installs for each user.

Re: Clone python environment on shared drive for multiple users to access

jcarlson — Thu, 18 Jan 2024 15:38:51 GMT

Seems more like a Python question than a Pro question. I've never heard of using a Python env from a shared drive, but that doesn't mean it can't work. Maybe @DanPatterson has some insights on this?

If you have an environment you want to share, it's fairly easy to export it to a text file and use that to replicate the same environment elsewhere. Especially if you use conda / mamba for the install.

Re: Clone python environment on shared drive for multiple users to access

DanPatterson — Thu, 18 Jan 2024 19:57:17 GMT

Beyond what it says in

Clone an environment—ArcGIS Pro | Documentation

with the related link regarding what to do with network access

Package Manager—ArcGIS Pro | Documentation

I don't do the cloud/network/sharing thing.... I work on a local machine only 😉

Re: Clone python environment on shared drive for multiple users to access

Dan_Joyce_OE — Fri, 23 Feb 2024 10:49:03 GMT

ArcGIS Pro 2.9.6

I've successfully cloned the default Python instance to a network file share folder. It took quite a while to clone, which was expected due to network latency.

Currently installing the boto3 and ReportLab modules into this environment.

Haven't yet tested if other users can select this environment.

Also haven't tested this setup to see if there is a significant impact on performance. I'll do some benchmarking and report back.

*** UPDATE ***

Installing the boto3 and ReportLab modules was successful.

Adding the shared Python environment using a UNC path looked like it worked, but when running my test script, it didn't appear to do anything. I think I read somewhere else that Python environments don't like UNC paths.

I then mapped the network location with a drive letter and re-added the shared environment.

This fixed the issue and my script ran as expected.

I measured the time taken (in seconds) for the script to:

Import the arcpy module
Clip a point feature class (stored in MS SQL Server)
Run a search cursor over the clipped features (10,697 features in file geodatabase stored locally)

I ran this test script using the default Pro Python environment and with the shared Python environment on the network location.

	Default env	Shared env	Delta
Initialise	0.065	0.093	+0.028 (+43%)
Clip	15.152	18.270	+3.118 (+21%)
Search Cursor	0.159	0.185	+0.026 (+16%)

This was just a simple test, but encouraging that the performance hit using a shared network location for the Python environment wasn't that big.

I haven't tested the impact of concurrent users accessing the shared Python environment.