Hi Folks,
I now have a specific case for python 2.6 or newer, namely tarfile lib
now properly reads bzip2 compressed files; needed for apt.py
(http://trac.osgeo.org/osgeo4w/wiki/pkg-apt,
http://trac.osgeo.org/osgeo4w/ticket/209). A fairly small need in the
grand o4w scheme but personally meaningful.
I'm willing to do some grunt work to move this forward but am not sure
what "rebuild all the python bindings for the various packages."
entails. If someone can give some specific examples or advice I'll start
on it.
cheers,
matt wilkie
--------------------------------------------
Geomatics Analyst
Information Management and Technology
Yukon Department of Environment
10 Burns Road * Whitehorse, Yukon * Y1A 4Y9
867-667-8133 Tel * 867-393-7003 Fax
http://environmentyukon.gov.yk.ca/geomatics/
--------------------------------------------
On 16/12/2010 9:39 AM, Frank Warmerdam wrote:
On 10-12-16 12:31 PM, Matt Wilkie wrote:
Hello All,
What specifically are the impediments to changing Osgeo4W python to 2.7? (or
any other number for that matter) I don't mean as an end user already using
o4w, but from the perspective of the project itself; what do we have to do to
enable us to ship python 2.7?
Matt,
I think the main barrier is the need to rebuild all the python bindings
for the various packages. That is a fairly substantial effort. What
advantages does Python 2.7 give us? Potentially we could do that as
part of a major refresh when also moving to GDAL 1.8 as our primary GDAL?
Best regards,
_______________________________________________
osgeo4w-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/osgeo4w-dev
