We have a web service that uses arcpy and needs to include information from a government web service that is only available via SOAP. We have used the suds-jurko library for the last few years without incident. After upgrading the server from 2.8 to 3.1.1 (and cloning a new environment) suds-jurko was missing from the list of packages to add. There is another popular SOAP package called zeep but that isn't on the list either.
The strange thing is that we have upgraded Pro on 2 different desktop computers to 3.1.1 and suds-jurko and zeep ARE both on the list. One of the desktops went from 2.8 to 3.0.1 and finally to 3.1.1. We tried doing a clean install of 3.0.1 yesterday to see if that would help, but the packages are still not on the list. We have admin privileges on both machines. The server is running a different OS from the desktops. Any ideas?
Solved! Go to Solution.
Thanks David. We found that the lists of available packages were different on the same installation of Pro for 2 different users. My manager could see suds-jurko as an option but I could not. We opened a case with ESRI and while they did not address why different users would have varying package selections on the same installation, they did provide step-by-step instructions for installing the package through the conda package manager (critical for a Python newbie such as myself). After following the steps below, suds-jurko showed up as desired in the list of installed packages in the Pro Package Manager.
1. Windows Search for Python Command Prompt (Running this prompt put me into the cloned, active Python environment)
2. Use the following commands: conda install -c conda-forge suds-jurko
Our team isn't on 3.1 yet but my best guess is ESRI dropped that package from the default installation. If you create a custom environment and then add suds-jurko or zeep through pip that should work, in my experience you don't need to go through the conda package manager unless your library uses precompiled binaries. You can also try installing 3.1.1 on a test machine and checking the packages included, there's always a chance your install screwed up during the python section.
Thanks David. We found that the lists of available packages were different on the same installation of Pro for 2 different users. My manager could see suds-jurko as an option but I could not. We opened a case with ESRI and while they did not address why different users would have varying package selections on the same installation, they did provide step-by-step instructions for installing the package through the conda package manager (critical for a Python newbie such as myself). After following the steps below, suds-jurko showed up as desired in the list of installed packages in the Pro Package Manager.
1. Windows Search for Python Command Prompt (Running this prompt put me into the cloned, active Python environment)
2. Use the following commands: conda install -c conda-forge suds-jurko