Select to view content in your preferred language

Version numbering, deprecation

185
1
Jump to solution
12-04-2024 05:56 AM
Labels (2)
jorisfrenkel
Frequent Contributor

I am a little bit confused about the version numbering of the ArcGIS API for Python.

I am trying to run a python script I wrote and tested with Python 3.9.16, together with ArcGIS Pro 3.1.1.

When I run this code in a Notebook in ArcGIS Online, I receive these messages:

/tmp/ipykernel_23/3079746621.py:164: DeprecatedWarning: shared_with is deprecated as of 2.3.0 and has been removed in 3.0.0. Use `Item.sharing` instead.
print (item.shared_with)

But I think I found that the latest version of the ArcGIS API is 2.4, not 3.0. So I guess this is a forward looking statement, and I should read it as "will be removed" instead of "has been removed"?

My second question is, why is there no message like that when I run this code locally with Python 3.9.16? Is that because this message has only been implemented starting from a later version of arcpy?

 

0 Kudos
1 Solution

Accepted Solutions
DanPatterson
MVP Esteemed Contributor

There are lots of deprecations on the horizon

arcgis-python-api/guide/02-api-overview/deprecation-notices.ipynb at 9deb1fbfe90ccf2fd73c45e777a1284...

and I suspect that the difference between running it on arcgis online and "locally" may be the issue, perhaps related to those differences (eg notebook vs script for instance).

You can forward-proof your scripts by keeping track of the release notes, and to find out the history of certain deprecations, you can always go back in time to find out when something was implemented or changed

arcgis-python-api/guide/02-api-overview/release_notes_240.ipynb at 9deb1fbfe90ccf2fd73c45e777a128477... 


... sort of retired...

View solution in original post

1 Reply
DanPatterson
MVP Esteemed Contributor

There are lots of deprecations on the horizon

arcgis-python-api/guide/02-api-overview/deprecation-notices.ipynb at 9deb1fbfe90ccf2fd73c45e777a1284...

and I suspect that the difference between running it on arcgis online and "locally" may be the issue, perhaps related to those differences (eg notebook vs script for instance).

You can forward-proof your scripts by keeping track of the release notes, and to find out the history of certain deprecations, you can always go back in time to find out when something was implemented or changed

arcgis-python-api/guide/02-api-overview/release_notes_240.ipynb at 9deb1fbfe90ccf2fd73c45e777a128477... 


... sort of retired...