[Django] #10923: Use thread-safe GEOS API if available

[Django]

#10923: Use thread-safe GEOS API if available
------------------------------+---------------------------------------------
Reporter: andrew_pendleton | Owner: nobody
Status: new | Milestone:
Component: GIS | Version: SVN
Keywords: | Stage: Unreviewed
Has_patch: 0 |
------------------------------+---------------------------------------------
The number of configurations under which GeoDjango can be used is limited
by its relative lack of thread-safety as compared to the rest of the
framework, mainly due to the lack of thread-safety of underlying libraries
like GEOS. The latest release of GEOS adds a thread-safe C API (proposed
in [http://trac.osgeo.org/geos/wiki/RFC3], tracked in
[http://trac.osgeo.org/geos/ticket/210], and committed prior to the
release of GEOS 3.1.0), so GeoDjango should use it if it's available.

--
Ticket URL: <http://code.djangoproject.com/ticket/10923>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#10923: Use thread-safe GEOS API if available

---------------------------------------+------------------------------------
Reporter: andrew_pendleton | Owner: jbronn
Status: new | Milestone: 1.2
Component: GIS | Version: SVN
Resolution: | Keywords: geos thread safe safety
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------+------------------------------------
Changes (by jbronn):

* needs_better_patch: => 0
* needs_tests: => 0
* owner: nobody => jbronn
* milestone: => 1.2
* keywords: => geos thread safe safety
* needs_docs: => 0

Comment:

See also the !GeoDjango [mercurial branch for a thread-safe GEOS interface
http://geodjango.org/hg/gis-ts/].

--
Ticket URL: <http://code.djangoproject.com/ticket/10923#comment:1>

[Django]

#10923: Use thread-safe GEOS API if available

---------------------------------------+------------------------------------
Reporter: andrew_pendleton | Owner: jbronn
Status: new | Milestone: 1.2
Component: GIS | Version: SVN
Resolution: | Keywords: geos thread safe safety
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------+------------------------------------

Comment (by jbronn):

See also the !GeoDjango [http://geodjango.org/hg/gis-ts/ mercurial branch
for a thread-safe GEOS interface]. Thanks to a dev known as tazle, we
have a beginning implementation, however, it's a non-trivial addition that
can benefit from additional testing.

--
Ticket URL: <http://code.djangoproject.com/ticket/10923#comment:2>

[Django]

#10923: Use thread-safe GEOS API if available

---------------------------------------+------------------------------------
Reporter: andrew_pendleton | Owner: jbronn
Status: new | Milestone: 1.2
Component: GIS | Version: SVN
Resolution: | Keywords: geos thread safe safety

Stage: Accepted | Has_patch: 0

Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------+------------------------------------

Changes (by Alex):

* stage: Unreviewed => Accepted

--
Ticket URL: <http://code.djangoproject.com/ticket/10923#comment:3>

[Django]

#10923: Use thread-safe GEOS API if available

---------------------------------------+------------------------------------
Reporter: andrew_pendleton | Owner: jbronn

Status: closed | Milestone: 1.2
Component: GIS | Version: SVN
Resolution: fixed | Keywords: geos thread safe safety

Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------+------------------------------------

Changes (by jbronn):

* status: new => closed
* resolution: => fixed

Comment:

(In [12214]) Fixed #10923 -- The GEOS bindings now use the thread-safe
API, when applicable. Thanks, Tuure Laurinolli, for assistance in
developing this patch.

--
Ticket URL: <http://code.djangoproject.com/ticket/10923#comment:4>