#25961: remove handling of thread-non-safe GEOS functions
-------------------------------------+-------------------------------------
Reporter: sir-sigurd | Owner: sir-
Type: | sigurd
Cleanup/optimization | Status: assigned
Component: GIS | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by sir-sigurd):
Replying to [comment:3 claudep]:
> Feel free to go ahead, this is going above my head :-)
Actually changes in my PR are quite trivial (maybe I did too much in a
single commit):
* `GEOSFunc` from django/contrib/gis/geos/prototypes/threadsafe.py is
simplified because we know that GEOS always have thread-safe API
* `GEOSFunc` is merged with `GEOSFuncFactory` from
django/contrib/gis/geos/libgeos.py
* the rest stuff from django/contrib/gis/geos/prototypes/threadsafe.py is
moved in django/contrib/gis/geos/libgeos.py
--
Ticket URL: <https://code.djangoproject.com/ticket/25961#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.d033a33bbda28295d4b0a6c02ae4d33c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
