The 2.4.1 version of ArcGIS API for Python was released on April 7, 2025.
Happy coding!
Thanks @NicholasGiner1! I'm excited for the dependency graphs and the SeDF updates.
Unfortunately, I'm having trouble installing 2.4.1 in my Pro 3.4.2 environment (arcgispro-py3-clone). When I follow the instructions in Using ArcGIS Pro 3.0 and later | ArcGIS API for Python > Upgrade Package it only updates to 2.4.0.1.
conda install -c esri arcgis arcgis-mapping
If I add the arcgis=2.4.1 release number to the command, I get the following errors:
├─ pin-3 is not installable because it requires
│ └─ python 3.11** , which conflicts with any installable versions previously reported;
└─ truststore 0.9.1.* is not installable because it conflicts with any installable versions previously reported.
The first one doesn't make much sense to me because I'm on Python 3.11.10 (which is what Pro installed). I don't really know what to make of the second one.
Has anyone else had this issue?
Hi @Sean-Sweeney,
I had the same issue. Try downloading ArcGIS Pro 3.5. It worked for me.
Thanks @PatriceLabbé! I haven't had a chance to give 3.5 a try yet but this will be a good incentive to try it.
FYI for anyone thinking about upgrading to Pro 3.5 to get API for Python 2.4.1:
BUG-000176644 for ArcGIS Pro - Calculate Field does not honor active selection or layer filters when using a SQL expression on file geodatabase data, resulting in all rows being calculated.
Exact same issue here. Pro v 3.4.4.
Surely there must be another solution from ESRI other than 'just upgrade to Pro v3.5 especially with the bug that @Sean-Sweeney notes below.
@NicholasGiner1 - any way to successfully work around this error? There's no option in Pro's package manager to just update the arcgis package to 2.4.1.3, even though it shows the latest available version as that.
Following the ESRI guidance to use python command prompt results in the exact errors that Sean highlights above.
I tried updating the arcgis package to 2.4.1.3 using --no-deps to try and ignore the apparent dependencies conflicts, but that also doesn't work - fails with the same errors again.
Very frustrating, to say the least.