Currently when calling `GeoIP2.city()` and `GeoIP2.country()` the city and
country databases will be used respectively, but this is unnecessary as
the country database is merely a subset of the city database. It should be
possible to provide a path and attempt to open a database from three
possible candidates: `path`, `path / city`, and `path / country`. While a
minor incompatibility in that the city database may be used instead, this
also reduces the potential for mixing data from two different databases
where one might be outdated.
--
Ticket URL: <https://code.djangoproject.com/ticket/35100>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* has_patch: 0 => 1
Comment:
[https://github.com/django/django/pull/17718 PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/35100#comment:1>
* stage: Unreviewed => Accepted
--
Ticket URL: <https://code.djangoproject.com/ticket/35100#comment:2>
* needs_better_patch: 0 => 1
--
Ticket URL: <https://code.djangoproject.com/ticket/35100#comment:3>
* needs_better_patch: 1 => 0
Comment:
Rebased and fixed tests after #35092.
--
Ticket URL: <https://code.djangoproject.com/ticket/35100#comment:4>
* stage: Accepted => Ready for checkin
--
Ticket URL: <https://code.djangoproject.com/ticket/35100#comment:5>
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"40b5b1596f7505416bd30d5d7582b5a9004ea7d5" 40b5b15]:
{{{
#!CommitTicketReference repository=""
revision="40b5b1596f7505416bd30d5d7582b5a9004ea7d5"
Fixed #35100 -- Reworked GeoIP2 database initialization.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35100#comment:6>