#24152 closed Cleanup/optimization (fixed)
Deprecate GeoQuerySet aggregate methods
| Reported by: | Claude Paroz | Owned by: | nobody |
|---|---|---|---|
| Component: | GIS | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
In the trend of making GeoQuerySet as similar to QuerySet as possible, I'd suggest to deprecate the GeoQuerySet aggregation methods, as GIS aggregates (Union, Extent, Extent3D, MakeLine, Collect) are already available and usable like any other Django aggregate.
Change History (8)
comment:1 by , 10 years ago
| Has patch: | set |
|---|---|
| Needs documentation: | set |
comment:4 by , 10 years ago
| Needs documentation: | unset |
|---|---|
| Triage Stage: | Accepted → Ready for checkin |
comment:5 by , 10 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
https://github.com/django/django/pull/3920
I've not updated the documentation yet. Should this deprecation happen in 1.8 or are we too late?