hi devs,
the QGIS grant program [¹] has selected, amongst others, a proposal to
prepare OSGeo4W for transition from python 2 to python 3.
maybe it's also worth/needed for GRASS GIS to think on a python version
transition in a well considered way?!
is there yet any list (trac, wiki?) what is needed for GRASS GIS'
preparedness for python 3 to also switch to the new version in a
mid(?)/long(?) term?
Should we compile such a list if not already there?
see also from the PSC mailing list [²]:
"> Python 3 is heavily knocking on the door.
IMHO also the Python 3 is a grass-dev topic."
[¹] http://blog.qgis.org/2016/10/04/winning-qgis-grant-proposals-for-2016/
[²] https://lists.osgeo.org/pipermail/grass-psc/2016-September/001589.html
-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/GRASS-GIS-python-3-tp5289895.html
Sent from the Grass - Dev mailing list archive at Nabble.com.