On Wed, Mar 20, 2013 at 5:40 PM, Robert Lagacé <[email protected]> wrote: > Some information : > > Python 2.5 first release 2006, last release 2.5.6 May 26, 2011 - No more fix > or update > > Python 2.6 first release oct. 2008, last release 2.6.6 April 10, 2012 > security and bug fix until october 2013 > - features : prepare migration to Pyton 3.0+ > > Python 2.7 first relaese July 3, 2010, last release 2.7.3 April 9, 2012 > - features : inclusion of 3.1 features > > wxPython 2.8.12 - April 2011 - available for Python 2.7 , 2.6 (first version > 2.8.0 Dec 12, 2006 - Python version ??) > > wxPython 2.8.10 - May 2009 - available for Python 2.6, 2.5, 2.4 > > wxPython 2.8.8 - June 2008 - available for Python 2.5, 2.4, 2.3 > > wxPython 2.6.4 - June 2007 - available for Python 2.5, 2.4, 2.3 (first > verion 2.6.0 April 27, 2005 - Python version 2.4, 2.3) > > In preparation for migration to Python 3 (in some future), tools existe for > migrating from 2.6 and 2.7 but none from 2.5. > See : http://python3porting.com/ > > As previously mentionned, wxPython is not available for Python 3.+ but in > some future. > > So, requiring Python 2.6 for programming is the minimum. This will facilitate > the futur porting work. > For users, we make a recommandation for Python 2.6+ with a note that it may > work for version < 2.6 but without guaranty. > Consequently, wxPython 2.8.10 is required > > For GRASS 7, wxPython 2.8.12 should be required.
Thanks for the nice summary. wxPython 2.8.10 is probably still used so I would leave this as required version. We can reconsider it again (in a year or so). Anna > > Robert Lagacé > > ________________________________________ > De : [email protected] [[email protected]] de > la part de Anna Kratochvílová [[email protected]] > Date d'envoi : 20 mars 2013 11:26 > À : Pietro > Cc : grass-user grass-user; Michael Barton; GRASS developers list > Objet : Re: [GRASS-dev] [GRASS-user] minimal wxPython version > > Minimum wxPython version is changed in r55466 (I hope I haven't missed > any other places). > > On Wed, Mar 20, 2013 at 1:31 PM, Pietro <[email protected]> wrote: >> On Wed, Mar 20, 2013 at 12:02 PM, Newcomb, Doug <[email protected]> wrote: >>> By at least, do you mean looking at 2.6, 2.7 or 3.0 as well? >> >> +1 for python 2.6 that it is the default version in debian stable [0]... >> >> >> Moreover, the Python 2.6 [1] added compatibility functions in a >> future_builtins module and a -3 switch to warn about usages that will >> become unsupported in 3.0... >> Therefore if we require python2.6, we can start to think about >> cleaning the python code and start to use the "future_builtins" >> modules. > > Yes, python3 is probably inevitable so we should prepare for it. > >> >> Concerning GRASS and python 3.X, I think that the biggest problem is >> the WxPython, at the moment only the develop version Phoneix[2] it is >> working with python 3. > > I think a lot of other projects are in the same situation so I hope > Phoenix will become more stable soon. It will take some time to update > wxGUI to work with it but in theory there shouldn't be any major > problems. A lot of small problems will appear, often because some > parts of the gui code is a mess (usually some gui layout parts) and > the newer wxPython doesn't accept it. > > > So any other opinions on Python version? > > Anna > _______________________________________________ > grass-dev mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/grass-dev _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
