Opened 93 minutes ago
#36988 new Bug
Limitation of supported GeoIP databases is too tight
| Reported by: | rami | Owned by: | |
|---|---|---|---|
| Component: | GIS | Version: | 6.0 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
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?
Note:
See TracTickets
for help on using tickets.