You can always use shell. But this is a question about 1) the graphical interface, and 2) python libraries for advanced commands and use in scripting.
Michael ____________________ C. Michael Barton Director, Center for Social Dynamics & Complexity Professor of Anthropology, School of Human Evolution & Social Change Arizona State University voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC) fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC) www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu On Mar 20, 2013, at 10:31 AM, kapo coulibaly <kmcou...@gmail.com> wrote: > How about sticking with shell? We wouldn't worry about endless version issues. > > On Wed, Mar 20, 2013 at 11:56 AM, Pietro <peter.z...@gmail.com> wrote: > Hi Michael, > > On Wed, Mar 20, 2013 at 3:35 PM, Michael Barton <michael.bar...@asu.edu> > wrote: > > My understanding is that Python 3 is not backward compatible with Python 2. > > it is true, but we are not talking to require python3 instead of > python2, we are talking to require python2.6 instead of python2.4, > that it is not backward compatible. > > Changing python2.4 in python2.6 allow us to start preparing the code > to reduce the gap between python2 and python3. Therefore if one day in > the 2016 or later (may be for GRASS8), we decide to switch definitely > to python3 we should be able to switch without too much effort. > > Pietro > _______________________________________________ > grass-user mailing list > grass-u...@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-user >
_______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
