Python... currently at the end of the 3.6 series in Pro (aka, 3.6.10).
Various packages that are used in the ecosystem are about to begin retiring 3.6.x.
For example... numpy will be saying goodbye
NEP 29 - Dropping Python version support · Issue #66 · dask/community · GitHub
and, IPython
ipython/version7.rst at master · ipython/ipython · GitHub
jupyterlab and jupyterlab-server... are they next?
Lots have been added to python 3.8.5 Documentation ... the last stable release
(don't forget to go back and check the 3.7 branch and look forward to 3.9/3.10 coming branches)
Is ArcMap the reason for the holdback?
Given that major and minor releases control substantive changes...
Releases and patches—ArcGIS Pro | Documentation
and minor change from 2.5 to 2.6 didn't produce a python change AND minor changes seem to occur once a year around UC, does that mean that we have to wait until next year?
Does anyone have any thoughts on this?
Kory Kramer I will flag you and perhaps the comments on Beta 2 about python versions could be fleshed out here
Solved! Go to Solution.
Another downside for not upgrading to 3.8 at least.
I work extensively with numpy and want to use typing without having to install extra packages. Current versions of numpy ( aka >= 1.19 ) allow for numpy-based typing, however....
Typing (:mod:`numpy.typing`) ============================ .. warning:: Some of the types in this module rely on features only present in the standard library in Python 3.8 and greater. If you want to use these types in earlier versions of Python, you should install the typing-extensions_ package
from.... numpy/__init__.py at master · numpy/numpy · GitHub
Not a biggie for most, but for those that think code documentation is as important as the code, this is becoming a limitation
I would still love to hear the reasons python versions lag. Perhaps, it is time for streams of ArcGIS Pro
Not for a while is the short of it.
Hello everybody,
Same thing happening to Python 3.7...
Numpy dropped support in december (NEP29: https://numpy.org/neps/nep-0029-deprecation_policy.html#drop-schedule), and the drop is cascading among the community (xarray, pandas, ...)
Do you know when ArcGis Pro will support Python 3.8 or newer ?