<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
It seems like it would be a fairly common case that an osgeo4w user would 1) only use a small subset of the available packages 2) eventually need to upgrade a package due to external dependencies before everybody else is ready. This seems especially likely where core components are concerned (Python, ogr, etc.) Are there docs / email threads addressing? Surely somebody else has tried to upgrade python or will soon?<br><br>> Subject: RE: [osgeo4w-dev] Python 2.6<br>> Date: Wed, 6 Jan 2010 13:21:54 -0500<br>> From: David.Sampson@NRCan-RNCan.gc.ca<br>> To: warmerdam@pobox.com<br>> CC: cullepm3@hotmail.com; osgeo4w-dev@lists.osgeo.org<br>> <br>> Fair enough,<br>> <br>> Just thought if it was a resource issue I could have helped.<br>> <br>> I have run into instances where some external libs req 2.6. But taking<br>> on the building of one lib for a specific task would certainly be less<br>> disruptive.<br>> <br>> Just thought I would offer.<br>> <br>> Cheers <br>> <br>> > -----Original Message-----<br>> > From: osgeo4w-dev-bounces@lists.osgeo.org <br>> > [mailto:osgeo4w-dev-bounces@lists.osgeo.org] On Behalf Of <br>> > Frank Warmerdam<br>> > Sent: Wednesday, January 06, 2010 12:41<br>> > To: Sampson, David<br>> > Cc: Patrick Cullen; osgeo4w-dev@lists.osgeo.org<br>> > Subject: Re: [osgeo4w-dev] Python 2.6<br>> > <br>> > Sampson, David wrote:<br>> > > Hey Folks.<br>> > > <br>> > > A. Would it help if I lent a hand? I just recently learnt how to <br>> > > handle SWIG for python and also posted a message to OSGEO discuss <br>> > > concerning migrating to Python 3.0<br>> > > <br>> > > B. How do I find out what modules? <br>> > > <br>> > > C. Could building a script help us in the future? Especially with <br>> > > migrating to 3.x?<br>> > > <br>> > > D. I could always build inside a virtual winxp box on my <br>> > linux system <br>> > > at home. A mini build env?<br>> > <br>> > Dave,<br>> > <br>> > The various python modules are already "owned" by packagers <br>> > and it could be distruptive to have someone else drop in and <br>> > try to replace them all without necessarily knowing the <br>> > special conditions the original packagers accounted for. I <br>> > would prefer a move to Python 2.6 take place as part of an <br>> > agreed step by all the OSGeo4W stakeholders.<br>> > <br>> > Personally, I'm not clear on benefits of Python 2.6 that <br>> > would justify a large amount of disruption.<br>> > <br>> > Best regards,<br>> > -- <br>> > ---------------------------------------+----------------------<br>> > ----------<br>> > ---------------------------------------+------<br>> > I set the clouds in motion - turn up | Frank Warmerdam, <br>> > warmerdam@pobox.com<br>> > light and sound - activate the windows | http://pobox.com/~warmerdam<br>> > and watch the world go round - Rush | Geospatial <br>> > Programmer for Rent<br>> > <br>> > _______________________________________________<br>> > osgeo4w-dev mailing list<br>> > osgeo4w-dev@lists.osgeo.org<br>> > http://lists.osgeo.org/mailman/listinfo/osgeo4w-dev<br>> > <br> </body>
</html>