#36988: Limitation of supported GeoIP databases is too tight
----------------------+--------------------------------------
Reporter: rami | Type: Bug
Status: new | Component: GIS
Version: 6.0 | Severity: Normal
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------+--------------------------------------
Starting in Django 5.1, Django ships with a [list of allowed GeoIP
database
types](https://github.com/django/django/blame/main/django/contrib/gis/geoip2.py):
{{{
SUPPORTED_DATABASE_TYPES = {
"DBIP-City-Lite",
"DBIP-Country-Lite",
"GeoIP2-City",
"GeoIP2-Country",
"GeoLite2-City",
"GeoLite2-Country",
}
}}}
It seems weird that Django seems to be enforcing where I am getting my
databases from. We've always been using the database freely available from
[here](https://github.com/geoacumen/geoacumen-country), which has the type
"Geoacumen-Country".
Is it really intended that I need to monkeypatch Django to use this GeoIP
database from a source that is not known to Django? Should this list
extensible in some official way?
--
Ticket URL: <https://code.djangoproject.com/ticket/36988>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019cfb4bb108-ac728bdc-441a-4636-9647-12b3755b3ef7-000000%40eu-central-1.amazonses.com.
