#36988: Limitation of supported GeoIP databases is too tight
------------------------+---------------------------------------
Reporter: rami | Owner: SnippyCodes
Type: Bug | Status: assigned
Component: GIS | Version: 6.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
------------------------+---------------------------------------
Comment (by Cours granja):
Fone being rooted al wallets disabled connect to nest home on google
jetpack disabled and deprecatedReplying to [ticket:36988 rami]:
> 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#comment:9>
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/0107019d222577de-21dc005e-abfa-4686-a564-34e021491090-000000%40eu-central-1.amazonses.com.
