Are python scripts for GRASS written with the __future__ module so they
can be used with python3?
I'm writing all new code with python3 (and will convert the python2
scripts as needed using 2to3) and would like to be able to remove python2.
I'm looking for a tool to tell me which installed applications require
python; I know that grass7.3.svn does.
Regards,
Rich
Rich Shepard wrote
Are python scripts for GRASS written with the __future__ module so they
can be used with python3?I'm writing all new code with python3 (and will convert the python2
scripts as needed using 2to3) and would like to be able to remove python2.
I'm looking for a tool to tell me which installed applications require
python; I know that grass7.3.svn does.
as stated in REQUIREMENTS to compile GRASS GIS 7 [1]
Python >= 2.6 (for temporal framework, scripts, wxGUI, and ctypes
interface)
Note: Python 3 support is still in development
some more discussions in [2] and [3]; maybe more in later discussions on the
dev ML.
[1] https://grass.osgeo.org/grass72/source/snapshot/REQUIREMENTS.html
[2]
http://osgeo-org.1560.x6.nabble.com/GRASS-GIS-2708-Run-GRASS-with-Python3-td5215769.html
[3] https://trac.osgeo.org/grass/ticket/2708
-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Python3-with-GRASS-tp5317418p5317419.html
Sent from the Grass - Users mailing list archive at Nabble.com.
On Sun, 16 Apr 2017, Helmut Kudrnovsky wrote:
as stated in REQUIREMENTS to compile GRASS GIS 7 [1]
Note: Python 3 support is still in development
Helmut,
My question was not as well formed as it should have been. I wonder how
much closer to useful python3 support the development version has come.
Thanks for the other URLs,
Rich
On Sun, 16 Apr 2017, Rich Shepard wrote:
My question was not as well formed as it should have been. I wonder how
much closer to useful python3 support the development version has come.
Helmut,
Zarch's thread from a couple of years ago is interesting. Has any
developer run 2to3 on python2 code (changing, for example, python2 strings
to python3 bytes and python2 unicode strings to python3 strings)?
My understanding is that python3's 2to3 does most syntax changes for us.
Regards,
Rich
Rich Shepard wrote
On Sun, 16 Apr 2017, Helmut Kudrnovsky wrote:
as stated in REQUIREMENTS to compile GRASS GIS 7 [1]
Note: Python 3 support is still in developmentHelmut,
My question was not as well formed as it should have been. I wonder how
much closer to useful python3 support the development version has come.Thanks for the other URLs,
when you do a search in the dev ML about python 3:
https://grass.osgeo.org/documentation/search-engine/
there are quite a lot of entries about python 3 discussions.
AFAIU there is no finally decided conclusion about python 3 support;
so the above mentioned statement may be still valid. others may have a
deeper insight.
-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Python3-with-GRASS-tp5317418p5317441.html
Sent from the Grass - Users mailing list archive at Nabble.com.
On Sun, 16 Apr 2017, Helmut Kudrnovsky wrote:
when you do a search in the dev ML about python 3:
Helmut,
I don't follow the dev maillist; didn't think of searching the archives
for it.
AFAIU there is no finally decided conclusion about python3 support; so the
above mentioned statement may be still valid. others may have a deeper
insight.
Okay. I'll cast a user vote for python3 support as soon as possible as
python2 has officially be deprecated.
Rich
Rich Shepard wrote
On Sun, 16 Apr 2017, Helmut Kudrnovsky wrote:
as stated in REQUIREMENTS to compile GRASS GIS 7 [1]
Note: Python 3 support is still in developmentHelmut,
My question was not as well formed as it should have been. I wonder how
much closer to useful python3 support the development version has come.Thanks for the other URLs,
Rich
_______________________________________________
grass-user mailing list
grass-user@.osgeo
AFAIU wxpython wasn't yet some kind of fully python 3 compatible on all
platforms.
Grass GUI is based on wxpython; therefore still a strong relation to the
python 2-line.
See
https://lists.osgeo.org/pipermail/grass-dev/2017-April/084781.html
So, there may be now a stronger momentum to get GRASS more python3 aware, as
the new wxpython engine is it now.
-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Python3-with-GRASS-tp5317418p5317601.html
Sent from the Grass - Users mailing list archive at Nabble.com.