Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#22655 closed Bug (fixed)

strictly_above vs strictly_below

Reported by: anonymous Owned by: nobody
Component: Documentation Version: 1.7-beta-2
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: yes UI/UX: no

Description

Strictly below has the same description as strictly above
https://docs.djangoproject.com/en/1.7/ref/contrib/gis/geoquerysets/#strictly-above

Change History (5)

comment:1 Changed 4 years ago by Tim Graham

Easy pickings: set
Triage Stage: UnreviewedAccepted
Type: UncategorizedBug

comment:3 Changed 4 years ago by Tim Graham <timograham@…>

Resolution: fixed
Status: newclosed

In 2f43229c2f044207f193e753baf1bd3fb6164da4:

Fixed #22655 -- Fixed GeoQuerySet doc about strictly_below

The paragraph was a copy of strictly_above.

comment:4 Changed 4 years ago by Tim Graham <timograham@…>

In 269291019ec2dddddd6dd3b9833a37e7b94944ab:

[1.7.x] Fixed #22655 -- Fixed GeoQuerySet doc about strictly_below

The paragraph was a copy of strictly_above.

Backport of 2f43229c2f from master

comment:5 Changed 4 years ago by Tim Graham <timograham@…>

In 6a2f8985c13e5524d397b48951d6de982544a71a:

[1.6.x] Fixed #22655 -- Fixed GeoQuerySet doc about strictly_below

The paragraph was a copy of strictly_above.

Backport of 2f43229c2f from master

Note: See TracTickets for help on using tickets.
Back to Top