<div dir="ltr">+1 to dropping the SWIG bindings.<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Nov 25, 2020 at 1:37 PM Mike Taves <<a href="mailto:mwtoews@gmail.com">mwtoews@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi all,<br>
<br>
SWIG bindings have existed as part of the core GEOS library since<br>
early development, however they have not received much attention in<br>
many years.<br>
<br>
I've (quickly) prepared two options for consideration:<br>
<br>
Option one: Drop Python SWIG bindings<br>
<a href="https://github.com/mwtoews/geos/pull/1" rel="noreferrer" target="_blank">https://github.com/mwtoews/geos/pull/1</a><br>
<br>
This keeps the SWIG interface for Ruby bindings, which is packed by<br>
(e.g.) Ubuntu; see <a href="https://packages.ubuntu.com/xenial/ruby/ruby-geos" rel="noreferrer" target="_blank">https://packages.ubuntu.com/xenial/ruby/ruby-geos</a><br>
However, it drops the unsupported Python 2 SWIG bindings. Python users<br>
can use either Shapely or PyGEOS.<br>
<br>
Option two: Drop SWIG bindings, including for Ruby and Python<br>
<a href="https://github.com/mwtoews/geos/pull/2" rel="noreferrer" target="_blank">https://github.com/mwtoews/geos/pull/2</a><br>
<br>
This drops the whole SWIG interface.<br>
Note that Ruby users can access GEOS bindings via RGeo<br>
<a href="https://github.com/rgeo/rgeo" rel="noreferrer" target="_blank">https://github.com/rgeo/rgeo</a>, which has a steady history of active<br>
contributions; see <a href="https://github.com/rgeo/rgeo/graphs/contributors" rel="noreferrer" target="_blank">https://github.com/rgeo/rgeo/graphs/contributors</a><br>
Another idea is to move the SWIG Ruby bindings into a separate repo,<br>
similar to php-geos <a href="https://git.osgeo.org/gitea/geos/php-geos" rel="noreferrer" target="_blank">https://git.osgeo.org/gitea/geos/php-geos</a>, however<br>
this would require a volunteer to step in.<br>
<br>
Any thoughts to either proposal? And if so, whether this should happen<br>
before or after the next release?<br>
_______________________________________________<br>
geos-devel mailing list<br>
<a href="mailto:geos-devel@lists.osgeo.org" target="_blank">geos-devel@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/geos-devel" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/geos-devel</a><br>
</blockquote></div>