Christopher Barker wrote: > 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 > > > Chris: I don't consider the pyrex GEOS interface I created for basemap a general-purpose binding - it's limited to the only the functionality that basemap needs. The ability of pyrex to do loops in C makes it a lot faster than the Shapely ctypes interface though. I have corresponded with Sean Gillies about this (and the LGPL licensing issue), and as a result I think Shapley 2.0 will be based on Pyrex and will have a BSD license. Perhaps then I can switch basemap back to using it.
Eric mentioned the fact that ctypes often has a hard time finding the shared library to load. I view this as a potential support nightmare for matplotlib if we use ctypes to interface with external libs, which might be installed anywhere. You can't even tell ctypes where to look - it's hard-coded into the Shapely __init__ and there's no way I can see to override the search path that ctypes uses. -Jeff -- Jeffrey S. Whitaker Phone : (303)497-6313 Meteorologist FAX : (303)497-6449 NOAA/OAR/PSD R/PSD1 Email : [EMAIL PROTECTED] 325 Broadway Office : Skaggs Research Cntr 1D-124 Boulder, CO, USA 80303-3328 Web : http://tinyurl.com/5telg ------------------------------------------------------------------------- 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
