Jeff, as you mentioned license as one issue in not using shapely, I thought you might be interested in this:
-------- Original Message -------- Subject: [Community] Proposal to change Shapely license from LGPL to BSD From: Sean Gillies <[EMAIL PROTECTED]> I propose that the Shapely license be changed to the 3 clause modified BSD used by OWSLib, GeoJSON, Rtree, and WorldMill. I choose LGPL orginally to match the GEOS license, but I think consistency across the new GIS-Python projects is more important. -------- As for ctypes vs. pyrex -- I find it ironic that you've chosen pyrex for dependency reasons -- there are lot of folks that using ctypes to asve the hassles of compiliation, particularly on Windows (see geoGjango, for instance). But I guess MPL required compilation anyway. I'm just poking at this 'cause I'd really like to see as little redundancy of python bindings for stuff as possible. WE alrady have geos bound by ogr, shapely (I think geoDjango), and who knows who else. Oh well, we all need to do what works best for our needs. I guess it's real credit to tools like swig, ctypes and pyrex (and python itself) that anyone would even consider writing their own bindings to something! -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
