#17756: GeoDjango missing pyspatialite support
-----------------------------+-----------------------------------------
     Reporter:  danols       |                    Owner:
         Type:  New feature  |                   Status:  new
    Component:  GIS          |                  Version:  master
     Severity:  Normal       |               Resolution:
     Keywords:               |             Triage Stage:  Someday/Maybe
    Has patch:  1            |      Needs documentation:  0
  Needs tests:  0            |  Patch needs improvement:  1
Easy pickings:  0            |                    UI/UX:  0
-----------------------------+-----------------------------------------

Comment (by ramiro):

 Replying to [comment:23 anentropic]:
 > Just dropping in to say anything that can ease the pain of setting up
 GeoDjango is much appreciated.  I'm trying to do it primarily via Homebrew
 and Pip... it'd be nice if it worked. The current instructions all lead to
 various dead ends
 >
 > I'm currently stuck here:
 > http://stackoverflow.com/questions/11093593/python-the-pysqlite-library-
 does-not-support-c-extension-loading

 The answer to that SO question is the same as the one the Geodjango docs
 have mentioned for some time:
 
https://docs.djangoproject.com/en/1.6/ref/contrib/gis/install/spatialite/#pysqlite2


 > [...]
 >
 > Can a core dev please set this back to 'Accepted' as it had previously
 been marked?

 Having tried the pyspatialite path myself recently, even with the latest
 development code, and getting the segmentation faults Anssi mentioned in
 comment:18 back in Jul '12 when trying to execute syncdb seems to indicate
 that it hasn't yet reached a point where we can:

 * Support pypatialite by replacing the module used by the ''main'' SQLite
 Django DB backend.
 * Recommend it as the easiest path to get GIS support with SQLite.

 and that the documented process of using platform-packages plus possibly
 building pysqlite2 with a modified configuration still is the safest
 strategy to reach success.

 Because of this, I think the 'someday/maybe' tag is appropiate at this
 point.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/17756#comment:26>
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/064.fd8dd9fcb42389803aa4bbd077440b76%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to