>I see two options: a) just publish the best practice and leave the packages alone, > and b) go ahead and make the changes, test, and apologize if necessary.
Actually I just talked myself into (a). I've enough work to do with projects closer to heart, like getting the register-python package working reliably on x64. ;-) -matt -- View this message in context: http://osgeo-org.1560.n6.nabble.com/osgeo4w-162-python-library-availability-tp3767247p4373911.html Sent from the osgeo4w-dev -- OSGeo Win32 Installer List mailing list archive at Nabble.com. _______________________________________________ osgeo4w-dev mailing list osgeo4w-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/osgeo4w-dev
