#26333: GIS geometries classes should be deconstructibles.
-------------------------------------+-------------------------------------
Reporter: simondrabble | Owner: niconoe
Type: Bug | Status: assigned
Component: GIS | Version: 1.8
Severity: Normal | Resolution:
Keywords: makemigration gis | Triage Stage: Accepted
point pointfield |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by niconoe):
* has_patch: 0 => 1
Comment:
Just created a pull request for this, testing various geometries with
various constructors.
Should I also write more functional tests to make sure the initial issue
is solved (and that migration actually works with `Point`), or is testing
that those are `deconstructible` enough?
--
Ticket URL: <https://code.djangoproject.com/ticket/26333#comment:6>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.956a0aefe8bd038a4ff5241ef20c4fbf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
