[osgeo4w-dev] python 2.7 as default: would anything significant break?

Martin Landa landa.martin at gmail.com
Tue Oct 4 04:54:41 EDT 2011

2011/10/4 Matt Wilkie <maphew at gmail.com>:
> I've been reviewing the current state of Python 2.7 in Osgeo4w, and
> trying to figure out what the next steps are to move this project
> forward. I confess to being unsure what that might be. That coupled
> with the fact the testing repository setup.ini is not updateable at
> the moment got me wondering "well, what if we just made it the
> default, and fixed whatever breaks?".
> That would be fine with me, but I don't know what to with gass-devel,
> wxpython, mapnik and the other unknown packages
> (http://trac.osgeo.org/osgeo4w/wiki/RequiresPython) normally let alone
> how to test if they're broken! Soooo, what do you folks think? What
> specific things can we do to advance upgrading python?

grass also uses numpy, but it seems to be available [1].


[1] http://sourceforge.net/projects/numpy/files/NumPy/1.5.1/numpy-1.5.1-win32-superpack-python2.7.exe/download

Martin Landa <landa.martin gmail.com> * http://geo.fsv.cvut.cz/~landa

More information about the osgeo4w-dev mailing list