#24673: Extend GeoDjango docs with info about pros and cons
-------------------------------+--------------------
Reporter: int-ua | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: 1.8
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------
Installing PostGIS and all these libraries is really time-consuming and
I'm not even sure what are the benefits in case I just want a simple
lat/lon fields.
P. S. IMHO all GeoDjango docs could use some improvement or review with
some newcomers. It looks like it was written without trying to understand
what reader really wants and without considering all possible use cases.
It's not even clear that it's safe to replace
django.db.backends.postgresql_psycopg2 for existing project.
--
Ticket URL: <https://code.djangoproject.com/ticket/24673>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/049.465ecd0ba4f4c5bcfc3db577fd6e4b49%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
