topic Re: arcgis.features and GeoAccessor error when trying to do import after update to 3.4 in Python Questions

arcgis.features and GeoAccessor error when trying to do import after update to 3.4

GISDepartmentMFM — Wed, 18 Dec 2024 19:21:35 GMT

posting this again here because I realized its probably a better place to ask this kind of question

hello,

I have been using from arcgis.features import GeoAccessor, GeoSeriesAccessor to make my layers from data frame for a good while now. However after updating to 3.4 when I try to import the following error occurs :

from arcgis.features import GeoAccessor, GeoSeriesAccessor
Traceback (most recent call last):
 File "<string>", line 1, in <module>
 File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\Lib\site-packages\arcgis\__init__.py", line 3, in <module>
 from arcgis.auth.tools import LazyLoader
 File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\Lib\site-packages\arcgis\auth\__init__.py", line 1, in <module>
 from .api import EsriSession
 File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\Lib\site-packages\arcgis\auth\api.py", line 8, in <module>
 from ._auth import (
 File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\Lib\site-packages\arcgis\auth\_auth\__init__.py", line 2, in <module>
 from ._pki import EsriPKIAuth
 File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\Lib\site-packages\arcgis\auth\_auth\_pki.py", line 4, in <module>
 from ..tools._lazy import LazyLoader
 File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\Lib\site-packages\arcgis\auth\tools\__init__.py", line 1, in <module>
 from .certificate import pfx_to_pem
 File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\Lib\site-packages\arcgis\auth\tools\certificate.py", line 9, in <module>
 from cryptography import x509
 File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\Lib\site-packages\cryptography\x509\__init__.py", line 7, in <module>
 from cryptography.x509 import certificate_transparency, verification
 File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\Lib\site-packages\cryptography\x509\certificate_transparency.py", line 8, in <module>
 from cryptography.hazmat.bindings._rust import x509 as rust_x509
ImportError: DLL load failed while importing _rust: The specified procedure could not be found.

I have tried doing the import on a different computer that also has 3.4 and there is no error I fear that I may have to do a reinstall however I came here before doing that just incase there is a better option before doing that.

Edit1: turns out import arcgis gives the same error. Tried uninstalling cryptography so I could reinstall that one package but it failed to even unistall. The arcgis package does exist as an install.

Re: arcgis.features and GeoAccessor error when trying to do import after update to 3.4

DanPatterson — Wed, 18 Dec 2024 18:15:16 GMT

did you upgrade or do a new install? and did you update the arcgis module?

try

import arcgis arcgis.__version__ Out[2]: '2.4.0' from arcgis.features import GeoAccessor, GeoSeriesAccessor dir(GeoAccessor) ['_HASARCPY', '_HASSHAPELY', '__class__', '__delattr__', '__dict__', '__dir__', .... snip ....

Re: arcgis.features and GeoAccessor error when trying to do import after update to 3.4

GISDepartmentMFM — Wed, 18 Dec 2024 18:29:32 GMT

you see I cant even run

import arcgis

when i try to import I get the same error as before

I have not updated any arcgis modals

if by new install you mean clicking the notification arcgis was giving me and initiate the update where it uninstalled the old version and installed 3.4 then yes.

error given:

import arcgis Traceback (most recent call last): File "<string>", line 1, in <module> File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\Lib\site-packages\arcgis\__init__.py", line 3, in <module> from arcgis.auth.tools import LazyLoader File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\Lib\site-packages\arcgis\auth\__init__.py", line 1, in <module> from .api import EsriSession File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\Lib\site-packages\arcgis\auth\api.py", line 8, in <module> from ._auth import ( File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\Lib\site-packages\arcgis\auth\_auth\__init__.py", line 2, in <module> from ._pki import EsriPKIAuth File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\Lib\site-packages\arcgis\auth\_auth\_pki.py", line 4, in <module> from ..tools._lazy import LazyLoader File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\Lib\site-packages\arcgis\auth\tools\__init__.py", line 1, in <module> from .certificate import pfx_to_pem File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\Lib\site-packages\arcgis\auth\tools\certificate.py", line 9, in <module> from cryptography import x509 File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\Lib\site-packages\cryptography\x509\__init__.py", line 7, in <module> from cryptography.x509 import certificate_transparency, verification File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\Lib\site-packages\cryptography\x509\certificate_transparency.py", line 8, in <module> from cryptography.hazmat.bindings._rust import x509 as rust_x509 ImportError: DLL load failed while importing _rust: The specified procedure could not be found.

Re: arcgis.features and GeoAccessor error when trying to do import after update to 3.4

DanPatterson — Wed, 18 Dec 2024 20:16:23 GMT

Go to the Project menu select Package Manager and see if arcgis is installed.

If not see if you can install it in the arcgispro-py3 environment

or use conda (conda install arcgis) if you know how to use it,

otherwise

How To: Perform a Clean Uninstall and Reinstall of ArcGIS Pro

Re: arcgis.features and GeoAccessor error when trying to do import after update to 3.4

GISDepartmentMFM — Wed, 18 Dec 2024 20:21:14 GMT

ok so i had to dig deep for this one. since uninstalling from package manager didn't work i went into the python cmd and ran as admin. I first did 'conda remove cryptography --force', to un install cryptography since that's what the traceback was saying the issue was originating from. then i did 'conda clean --all' to just do general cleaning. After that 'conda install cryptography'. then tryed running import arcgis wich gave the same error as before however at the end there was somthing new:

from cryptography.x509 import certificate_transparency, verification File "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\Lib\site-packages\cryptography\x509\certificate_transparency.py", line 11, in <module> from cryptography.hazmat.bindings._rust import x509 as rust_x509 RuntimeError: OpenSSL 3.0's legacy provider failed to load. This is a fatal error by default, but cryptography supports running without legacy algorithms by setting the environment variable CRYPTOGRAPHY_OPENSSL_NO_LEGACY. If you did not expect this error, you have likely made a mistake with your OpenSSL configuration.

this is something new so i tried repairing openssl with 'set CRYPTOGRAPHY_OPENSSL_NO_LEGACY=1' and 'conda install -c conda-forge openssl'. still having the error. ok then well im already in this deep. so

First, remove both packages: Copyconda remove cryptography openssl --force Clean the conda environment: Copyconda clean --all Install OpenSSL: Copyconda install -c conda-forge openssl=3.1.4 Then install cryptography: Copyconda install -c conda-forge cryptography=41.0.7

after installing cryptography it did give me a bunch of conflict notifications but still tried it out and no import errors now! this process might bite me in the back in the future , unforces consequences and all that.

list of conflicts:

>conda install -c conda-forge cryptography=41.0.7 Channels: - conda-forge - defaults - esri Platform: win-64 Collecting package metadata (repodata.json): done Solving environment: failed SpecsConfigurationConflictError: Requested specs conflict with configured specs. requested specs: - cryptography=41.0.7 pinned specs: - esri/noarch::annotated-types==0.6.0=py_2 - defaults/win-64::anyio==3.5.0=py311haa95532_0 - esri/noarch::anywidget==0.9.13=py_1 - defaults/noarch::appdirs==1.4.4=pyhd3eb1b0_0 - arcgis=2.4 - esri/noarch::arcgis-mapping==4.30.0=py_305 - arcgispro=3.4 - arcpy=3.4 - arcpy-base=3.4 - defaults/noarch::argon2-cffi==21.3.0=pyhd3eb1b0_0 - defaults/win-64::argon2-cffi-bindings==21.2.0=py311h2bbff1b_0 - esri/win-64::arrow-cpp==16.1.0=4 - defaults/noarch::asttokens==2.0.5=pyhd3eb1b0_0 - esri/noarch::async-lru==2.0.4=py_0 - defaults/win-64::attrs==23.1.0=py311haa95532_0 - esri/win-64::aws-crt-cpp==0.27.4=0 - esri/win-64::aws-sdk-cpp-base==1.11.386=1 - esri/noarch::azure-core==1.12.0=py_0 - esri/noarch::azure-storage-blob==12.8.0=py_0 - esri/win-64::babel==2.11.0=py311_1 - defaults/win-64::beautifulsoup4==4.12.3=py311haa95532_0 - esri/win-64::black==23.10.1=py311_2 - defaults/win-64::blas==1.0=mkl - defaults/noarch::bleach==4.1.0=pyhd3eb1b0_0 - defaults/win-64::blinker==1.6.2=py311haa95532_0 - defaults/win-64::bottleneck==1.3.7=py311hd7041d2_0 - esri/win-64::brotli==1.1.0=1 - esri/win-64::brotli-bin==1.1.0=1 - defaults/win-64::brotli-python==1.0.9=py311hd77b12b_8 - esri/win-64::c-ares==1.19.1=0 - defaults/win-64::cachetools==5.3.3=py311haa95532_0 - conda-forge/noarch::certifi==2024.12.14=pyhd8ed1ab_0 - defaults/win-64::cffi==1.16.0=py311h2bbff1b_1 - esri/win-64::cftime==1.6.3=py311_0 - defaults/win-64::chardet==4.0.0=py311haa95532_1003 - defaults/noarch::charset-normalizer==3.3.2=pyhd3eb1b0_0 - defaults/win-64::click==8.1.7=py311haa95532_0 - defaults/win-64::cloudpickle==3.0.0=py311haa95532_0 - defaults/win-64::colorama==0.4.6=py311haa95532_0 - esri/noarch::comm==0.2.2=py_0 - defaults/win-64::contourpy==1.2.0=py311h59b6b97_0 - esri/win-64::cppzmq==4.9.0=0 - conda-forge/win-64::cryptography==42.0.1=py311h7cb4080_0 - defaults/noarch::cycler==0.11.0=pyhd3eb1b0_0 - defaults/win-64::cytoolz==0.12.2=py311h2bbff1b_0 - esri/noarch::dask==2023.3.2=py_0 - esri/noarch::dask-core==2023.3.2=py_0 - defaults/win-64::debugpy==1.6.7=py311hd77b12b_0 - defaults/noarch::decorator==5.1.1=pyhd3eb1b0_0 - defaults/noarch::defusedxml==0.7.1=pyhd3eb1b0_0 - esri/noarch::distributed==2023.3.2=py_0 - esri/win-64::dpcpp-cpp-rt==2022.2.1=arcgispro_19741 - defaults/win-64::entrypoints==0.4=py311haa95532_0 - defaults/win-64::et_xmlfile==1.1.0=py311haa95532_0 - esri/noarch::exceptiongroup==1.0.0rc9=pyhd8ed1ab_0 - defaults/noarch::executing==0.8.3=pyhd3eb1b0_0 - defaults/win-64::flake8==7.0.0=py311haa95532_0 - defaults/win-64::fonttools==4.51.0=py311h2bbff1b_0 - freetype=2.13 - defaults/win-64::fsspec==2024.6.1=py311haa95532_0 - esri/win-64::future==0.18.3=py311_0 - gdal=3.9.2 - esri/noarch::geomet==1.0.0=py_0 - defaults/win-64::greenlet==3.0.1=py311hd77b12b_0 - defaults/win-64::h11==0.14.0=py311haa95532_0 - h5py=3.10.0 - defaults/win-64::httpcore==1.0.2=py311haa95532_0 - defaults/win-64::httpx==0.27.0=py311haa95532_0 - esri/win-64::icc_rt==2022.2.1=arcgispro_19741 - defaults/win-64::idna==3.7=py311haa95532_0 - defaults/win-64::importlib-metadata==7.0.1=py311haa95532_0 - defaults/noarch::importlib_metadata==7.0.1=hd3eb1b0_0 - defaults/win-64::importlib_resources==6.4.0=py311haa95532_0 - esri/noarch::iniconfig==1.1.1=pyhd3eb1b0_0 - esri/win-64::intel-cmplr-lib-rt==2022.2.1=arcgispro_19741 - esri/win-64::intel-fortran-rt==2022.2.1=arcgispro_19741 - esri/win-64::intel-openmp==2022.2.1=arcgispro_19741 - esri/noarch::ipykernel==6.29.5=pyh5f5efe1_0 - esri/noarch::ipython==8.18.1=pyh3a91677_1 - defaults/noarch::ipython_genutils==0.2.0=pyhd3eb1b0_1 - esri/noarch::ipywidgets==8.1.5=py_0 - esri/noarch::isodate==0.6.0=py_0 - defaults/noarch::jdcal==1.4.1=pyhd3eb1b0_0 - esri/noarch::jedi==0.18.2=py_1 - defaults/win-64::jinja2==3.1.4=py311haa95532_0 - esri/win-64::jpeg==9e=0 - esri/noarch::json5==0.9.25=py_0 - defaults/win-64::jsonschema==4.19.2=py311haa95532_0 - defaults/win-64::jsonschema-specifications==2023.7.1=py311haa95532_0 - esri/noarch::jupyter-lsp==2.2.0=py_0 - esri/noarch::jupyter_client==8.6.0=py_0 - esri/noarch::jupyter_console==6.6.3=py_0 - esri/win-64::jupyter_core==5.5.1=py311_1 - esri/noarch::jupyter_events==0.10.0=py_0 - esri/noarch::jupyter_server==2.14.2=py_0 - defaults/win-64::jupyter_server_terminals==0.4.4=py311haa95532_1 - esri/noarch::jupyterlab==4.2.4=py_0 - esri/noarch::jupyterlab_pygments==0.3.0=py_1 - esri/noarch::jupyterlab_server==2.27.3=py_0 - esri/noarch::jupyterlab_widgets==3.0.13=py_0 - esri/win-64::keyring==24.3.0=py311_1 - defaults/win-64::kiwisolver==1.4.4=py311hd77b12b_0 - esri/win-64::krb5==1.21.3=1 - esri/win-64::libabseil==20230125.3=0 - esri/win-64::libbrotlicommon==1.1.0=1 - esri/win-64::libbrotlidec==1.1.0=1 - esri/win-64::libbrotlienc==1.1.0=1 - esri/win-64::libdeflate==1.20=1 - esri/win-64::libpng==1.6.43=1 - esri/win-64::libprotobuf==3.21.12=4 - esri/win-64::libsodium==1.0.18=5 - esri/win-64::libthrift==0.20.0=0 - esri/win-64::libtiff==4.6.0=4 - esri/win-64::libutf8proc==2.8.0=0 - esri/win-64::libxml2==2.12.9=arcgispro_0 - esri/win-64::libxslt==1.1.42=0 - defaults/win-64::locket==1.0.0=py311haa95532_0 - esri/win-64::lxml==5.3.0=py311_0 - defaults/win-64::lz4==4.3.2=py311h2bbff1b_0 - esri/win-64::lz4-c==1.9.4=1 - defaults/win-64::markupsafe==2.1.3=py311h2bbff1b_0 - matplotlib=3.6.3 - esri/win-64::matplotlib-base==3.6.3=py311_arcgispro_2 - defaults/win-64::matplotlib-inline==0.1.6=py311haa95532_0 - defaults/noarch::mccabe==0.7.0=pyhd3eb1b0_0 - defaults/win-64::mistune==2.0.4=py311haa95532_0 - mkl==2022.2.1=arcgispro_19755 - esri/win-64::mkl-service==2.4.1=py311_arcgispro_0 - esri/win-64::mkl_fft==1.3.10=py311_arcgispro_0 - esri/win-64::mkl_random==1.2.7=py311_arcgispro_0 - defaults/win-64::mpmath==1.3.0=py311haa95532_0 - defaults/win-64::msgpack-python==1.0.3=py311h59b6b97_0 - esri/noarch::msrest==0.6.21=py_0 - defaults/win-64::mypy_extensions==1.0.0=py311haa95532_0 - esri/noarch::nbclassic==1.1.0=py_1 - esri/noarch::nbclient==0.8.0=py_0 - esri/noarch::nbconvert==7.16.4=py_0 - esri/noarch::nbformat==5.10.4=py_0 - defaults/win-64::nest-asyncio==1.6.0=py311haa95532_0 - netcdf4=1.6.4 - defaults/win-64::networkx==3.3=py311haa95532_0 - esri/win-64::nlohmann_json==3.11.2=0 - defaults/noarch::nose==1.3.7=pyhd3eb1b0_1008 - notebook=7 - esri/noarch::notebook-shim==0.2.4=py_0 - esri/win-64::numexpr==2.8.4=py311_2 - numpy=1.24 - esri/win-64::numpy-base==1.24.3=py311_1 - esri/noarch::oauthlib==3.2.2=py_0 - defaults/noarch::olefile==0.46=pyhd3eb1b0_0 - defaults/win-64::openpyxl==3.1.2=py311h2bbff1b_0 - conda-forge/win-64::openssl==3.1.4=hcfcfb64_0 - esri/win-64::orc==2.0.0=0 - defaults/win-64::overrides==7.4.0=py311haa95532_0 - defaults/win-64::packaging==24.1=py311haa95532_0 - esri/win-64::pandas==2.0.2=py311_0 - defaults/noarch::pandocfilters==1.5.0=pyhd3eb1b0_0 - defaults/noarch::parso==0.8.3=pyhd3eb1b0_0 - defaults/win-64::partd==1.4.1=py311haa95532_0 - esri/noarch::pathspec==0.9.0=py_0 - defaults/win-64::patsy==0.5.6=py311haa95532_0 - esri/noarch::pefile==2022.5.30=pyhd8ed1ab_0 - defaults/noarch::pickleshare==0.7.5=pyhd3eb1b0_1003 - pillow=10.4 - esri/win-64::pip==23.3.2=py311_0 - defaults/win-64::platformdirs==3.10.0=py311haa95532_0 - defaults/win-64::pluggy==1.0.0=py311haa95532_1 - pro_notebook_integration=3.4 - esri/noarch::prometheus_client==0.20.0=py_0 - esri/noarch::prompt-toolkit==3.0.47=py_0 - esri/noarch::prompt_toolkit==3.0.47=0 - protobuf=4.21.12 - defaults/win-64::psutil==5.9.0=py311h2bbff1b_0 - esri/noarch::psygnal==0.11.0=py_0 - defaults/noarch::pure_eval==0.2.2=pyhd3eb1b0_0 - esri/noarch::puremagic==1.15=py_0 - esri/win-64::pyarrow==16.1.0=py311_2 - esri/win-64::pybind11==2.10.4=2 - esri/win-64::pybind11_json==0.2.13=2 - defaults/win-64::pycodestyle==2.11.1=py311haa95532_0 - defaults/noarch::pycparser==2.21=pyhd3eb1b0_0 - esri/noarch::pydantic==2.4.2=py_1 - esri/win-64::pydantic-core==2.10.1=py311_1 - defaults/win-64::pyflakes==3.2.0=py311haa95532_0 - esri/noarch::pygments==2.18.0=py_0 - esri/noarch::pyjwt==2.4.0=py_1 - esri/noarch::pylerc==4.0=py_0 - defaults/win-64::pyodbc==5.0.1=py311hd77b12b_0 - defaults/win-64::pyparsing==3.1.2=py311haa95532_0 - esri/noarch::pypdf==4.3.1=py_1 - defaults/win-64::pyshp==2.3.1=py311haa95532_0 - defaults/win-64::pysocks==1.7.1=py311haa95532_0 - esri/win-64::pyspnego==0.11.1=py311_0 - esri/win-64::pytest==7.4.3=py311_0 - python=3.11 - defaults/win-64::python-dateutil==2.9.0post0=py311haa95532_2 - defaults/win-64::python-fastjsonschema==2.16.2=py311haa95532_0 - esri/win-64::python-gssapi==1.8.3=py311_1 - defaults/win-64::python-json-logger==2.0.7=py311haa95532_0 - esri/win-64::pytz==2022.6=py311_0 - esri/win-64::pywin32-ctypes==0.2.0=py311_1 - esri/win-64::pywin32-security==306=py311_2 - defaults/win-64::pywinpty==2.0.10=py311h5da7b33_0 - defaults/win-64::pyyaml==6.0.1=py311h2bbff1b_0 - esri/win-64::pyzmq==25.1.2=py311_0 - esri/win-64::re2==2023.06.02=0 - defaults/win-64::referencing==0.30.2=py311haa95532_0 - defaults/win-64::regex==2023.10.3=py311h2bbff1b_0 - defaults/win-64::requests==2.31.0=py311haa95532_1 - esri/noarch::requests-gssapi==1.2.3=py_2 - esri/noarch::requests-kerberos==0.14.0=pyh424387f_4 - defaults/win-64::requests-oauthlib==2.0.0=py311haa95532_0 - esri/noarch::requests-toolbelt==1.0.0=py_0 - defaults/win-64::rfc3339-validator==0.1.4=py311haa95532_0 - defaults/win-64::rfc3986-validator==0.1.1=py311haa95532_0 - defaults/win-64::rpds-py==0.10.6=py311h062c2fa_0 - defaults/win-64::ruamel.yaml==0.17.21=py311h2bbff1b_0 - esri/noarch::saspy==4.3.2=py_1 - esri/win-64::scipy==1.9.3=py311_4 - defaults/win-64::seaborn==0.13.2=py311haa95532_0 - defaults/win-64::send2trash==1.8.2=py311haa95532_0 - esri/win-64::setuptools==74.1.2=py311_0 - esri/noarch::six==1.16.0=py_0 - esri/win-64::snappy==1.2.1=0 - defaults/win-64::sniffio==1.3.0=py311haa95532_0 - defaults/noarch::sortedcontainers==2.4.0=pyhd3eb1b0_0 - defaults/win-64::soupsieve==2.5=py311haa95532_0 - esri/win-64::sqlalchemy==2.0.32=py311_0 - esri/win-64::sqlite==3.46.1=0 - esri/win-64::sspilib==0.1.0=py311_0 - esri/noarch::stack_data==0.5.1=py_0 - defaults/win-64::statsmodels==0.14.0=py311hd7041d2_0 - esri/win-64::swat==1.13.3=py311_1 - esri/win-64::sympy==1.12=py311_0 - defaults/noarch::tblib==1.7.0=pyhd3eb1b0_0 - defaults/win-64::terminado==0.17.1=py311haa95532_0 - esri/noarch::testpath==0.5.0=py_0 - esri/noarch::tinycss2==1.1.1=py_0 - defaults/noarch::toml==0.10.2=pyhd3eb1b0_0 - defaults/win-64::tomli==2.0.1=py311haa95532_0 - defaults/win-64::toolz==0.12.0=py311haa95532_0 - defaults/win-64::tornado==6.3.3=py311h2bbff1b_0 - defaults/win-64::tqdm==4.66.5=py311h746a85d_0 - defaults/win-64::traitlets==5.14.3=py311haa95532_0 - esri/noarch::truststore==0.9.1=py_0 - defaults/win-64::typing-extensions==4.11.0=py311haa95532_0 - defaults/win-64::typing_extensions==4.11.0=py311haa95532_0 - defaults/noarch::tzdata==2024a=h04d1e81_0 - defaults/win-64::ujson==5.4.0=py311hd77b12b_0 - defaults/win-64::unicodedata2==15.1.0=py311h2bbff1b_0 - defaults/win-64::urllib3==2.2.2=py311haa95532_0 - defaults/win-64::vc==14.2=h21ff451_1 - conda-forge/win-64::vs2015_runtime==14.42.34433=hdffcdeb_23 - defaults/win-64::watchfiles==0.21.0=py311h062c2fa_0 - defaults/noarch::wcwidth==0.2.5=pyhd3eb1b0_0 - defaults/win-64::webencodings==0.5.1=py311haa95532_1 - defaults/win-64::websocket-client==1.8.0=py311haa95532_0 - defaults/win-64::wheel==0.44.0=py311haa95532_0 - esri/noarch::widgetsnbextension==4.0.13=py_0 - esri/win-64::win_inet_pton==1.1.0=py311_1 - esri/win-64::winkerberos==0.9.1=py311_0 - defaults/win-64::winpty==0.4.3=4 - defaults/win-64::wrapt==1.14.1=py311h2bbff1b_0 - defaults/win-64::xarray==2023.6.0=py311haa95532_0 - esri/win-64::xeus==3.0.5=0 - esri/win-64::xeus-python==0.15.8=py311_2 - esri/noarch::xeus-python-shell==0.6.3=1 - esri/noarch::xeus-python-shell-raw==0.6.3=py_1 - esri/win-64::xeus-zmq==1.0.2=3 - defaults/noarch::xlrd==2.0.1=pyhd3eb1b0_1 - defaults/win-64::xlwt==1.3.0=py311haa95532_0 - esri/win-64::xtl==0.7.5=0 - esri/win-64::xz==5.4.7=0 - esri/win-64::yaml==0.2.5=0 - esri/win-64::zeromq==4.3.5=0 - esri/noarch::zict==3.0.0=py_0 - defaults/win-64::zipp==3.17.0=py311haa95532_0 - esri/win-64::zlib==1.3.1=1 - esri/win-64::zlib-ng==2.1.6=2 - esri/win-64::zstd==1.5.6=1 Use 'conda config --show-sources' to look for 'pinned_specs' and 'track_features' configuration parameters. Pinned specs may also be defined in the file

Re: arcgis.features and GeoAccessor error when trying to do import after update to 3.4

DanPatterson — Wed, 18 Dec 2024 21:28:05 GMT

sounds like you might want to use a separate environment and you don't require arcpy and you use cryptography daily. you can install arcgis in a separate environment since it will use shapely if arcpy isn't present. If that environment doesn't work out, you have the recommended clean install/reinstall link.