Opened 8 years ago

Last modified 7 years ago

#28341 assigned Bug

GeometryField doesn't create GEOSGeometry objects lazily anymore — at Version 2

Reported by: Sergey Fedoseev Owned by: Sergey Fedoseev
Component: GIS Version: 1.8
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description (last modified by Sergey Fedoseev)

Bisected to e9103402c0fa873aea58a6a11dba510cd308cb84 on test project with this script:

import mock
import sys

with mock.patch('django.utils.six.moves.html_parser'):
    import django
    from django.test import TestCase
    from django.contrib.gis.geos import Point

from test_app.models import City


def side_effect(*args, **kwargs):
    sys.exit(1)


django.setup()


with mock.patch('django.contrib.gis.db.models.fields.Geometry.__init__', side_effect=side_effect):
    City.objects.first()

This laziness is declared in GeoDjango Tutorial.

According to the ticket's flags, the next step(s) to move this issue forward are:

  • To provide a patch by sending a pull request. Claim the ticket when you start working so that someone else doesn't duplicate effort. Before sending a pull request, review your work against the patch review checklist. Check the "Has patch" flag on the ticket after sending a pull request and include a link to the pull request in the ticket comment when making that update. The usual format is: [https://github.com/django/django/pull/#### PR].

Change History (2)

comment:1 by Sergey Fedoseev, 8 years ago

Owner: changed from nobody to Sergey Fedoseev
Status: newassigned

comment:2 by Sergey Fedoseev, 8 years ago

Description: modified (diff)
Note: See TracTickets for help on using tickets.
Back to Top